Hide teaming interest MCP tool
Mark a teaming interest as hidden so it is no longer surfaced in cross-user discovery searches. Pre-existing match records remain visible to both parties; the hidden interest itself is no longer browsable by non-owners. Reverse later with Reopen_Teaming_Interest. Owner-only.
- MCP tool name:
Hide_Teaming_Interest - Returns: Teaming interest MCP response
- Annotations: Not read only, destructive, idempotent, closed world
- Surfaces: GovTribe AI
Examples
Hide an interest when the user wants to pause new partner discovery without cancelling existing matches. Use the Withdraw teaming interest MCP tool instead when the user wants to cancel pending matches too.
Hide an open interest
{
"tool": "Search_Teaming_Interests",
"arguments": {
"teaming_interest_statuses": ["open"],
"fields_to_return": [
"govtribe_id",
"name",
"intent",
"teamable"
]
}
}{
"tool": "Hide_Teaming_Interest",
"arguments": {
"teaming_interest_id": "<teaming_interest_govtribe_id>"
}
}Related articles
- Teaming interest MCP response: Review the response shape returned by this tool.
- GovTribe AI: Review the GovTribe AI surface where this tool can be called.
- Source identifiers and record matching: Use GovTribe IDs and source identifiers when passing records between tools.
Get teaming messages
Read messages from a teaming conversation: pass teaming_match_id for a match conversation or teaming_interest_id (prime side) for the team-hub conversation. Returns up to 50 messages per page, oldest to newest, including system messages; page backward with `before`. Reading does NOT mark the conversation as read for the user. Only conversation participants can read.
Interaction state
Reads or persists canonical state for interactive MCP apps.