Skip to main content
Glama
Sign In
Enterprise Threads MCP Server

Enterprise Threads MCP Server

by baguskto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_mentions

Retrieve threads where you are mentioned to track conversations and engage with your audience.

Instructions

Get threads where you are mentioned

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_mentions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of mentions to retrieve
fieldsNoFields to retrieve from mentions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv5.1.0

TDQS

B3.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description alone must convey behavior. It clearly states the read operation, but adds no detail about pagination, ordering, or response structure. It is not misleading, but it is minimal for a tool without annotation support.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence of six words, front-loaded and free of unnecessary content. It is highly concise and to the point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with two optional parameters, and the description adequately states its function. However, it lacks any differentiation from the sibling 'search_mentions' and provides no hints about return format or edge cases, making it only minimally complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides descriptions for both parameters (limit and fields), achieving 100% coverage. The tool description adds no extra parameter semantics beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a clear verb 'Get' and a specific resource 'threads where you are mentioned', making the core purpose unambiguous. However, it does not explicitly distinguish this from sibling tools like search_mentions, so it misses full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as search_mentions or get_my_threads. There are no exclusions, preferred scenarios, or context hints beyond the basic purpose.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools