Get teaming messages MCP tool
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.
- MCP tool name:
Get_Teaming_Messages - Returns: Teaming messages MCP response
- Annotations: Read only, not destructive, idempotent, closed world
- Surfaces: GovTribe AI
Examples
Pass exactly one of teaming_match_id or teaming_interest_id. Use teaming_match_id for a match conversation, or a PRIME interest's teaming_interest_id for the team-hub conversation that exists once the prime locks in the team. Messages return oldest to newest, up to 50 per page (limit accepts 1–50, default 50). Reading never marks the conversation as read for the user.
Read a match conversation
Resolve the match first, then read its conversation.
{
"tool": "Search_Teaming_Matches",
"arguments": {
"fields_to_return": [
"govtribe_id",
"status",
"viewer_context",
"conversation_summary"
]
}
}{
"tool": "Get_Teaming_Messages",
"arguments": {
"teaming_match_id": "<teaming_match_govtribe_id>"
}
}Read a team-hub conversation as the prime
{
"tool": "Get_Teaming_Messages",
"arguments": {
"teaming_interest_id": "<prime_teaming_interest_govtribe_id>"
}
}Page backward through older messages
While has_older is true, pass the oldest returned created_at as before.
{
"tool": "Get_Teaming_Messages",
"arguments": {
"teaming_match_id": "<teaming_match_govtribe_id>",
"before": "2026-06-08T14:05:00Z",
"limit": 50
}
}Related articles
- Teaming messages 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.
GovTribe Documentation
Search and retrieve GovTribe documentation articles and article segments using query, article selectors, and token-budgeted content retrieval.
Hide teaming interest
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.