Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search SocialFetch docs

docs_search
Read-onlyIdempotent

Search SocialFetch documentation for API and SDK answers with natural-language queries, then locate response fields and cross-platform author/timestamp naming guidance.

Instructions

Search SocialFetch docs for API/SDK questions. For response fields use docs_read (defaults to outline). For cross-platform author/timestamp naming, search field crosswalk or read /product/ask-ai/field-crosswalk.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "docs_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of docs results to return.
queryYesNatural-language description of what to find in SocialFetch docs (at least 2 characters).
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.
currentDocsPathnameNoOptional current SocialFetch docs pathname, such as /docs/sdk or /product/guides/..., to boost nearby results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds useful disambiguation and a fallback pointer but says nothing about how ranking works, what a result looks like, or how limit/currentDocsPathname affect output. Adequate beyond annotations, not rich.

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?

Three short sentences, front-loaded with the core purpose, then the alternative and the fallback path. No filler or repeated information from the schema.

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

Completeness4/5

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

Covers the routing need for a six-parameter search tool whose parameters are fully documented. The mild gap is the absence of any statement about result shape (snippets vs. sections) in a tool with no output schema, though the docs_read reference partially implies it.

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?

Schema description coverage is 100%, so every parameter (query, context, llm_model, conversation_id, limit, currentDocsPathname) is already documented in the schema. The description adds only an implicit hint about what query text to use ('field crosswalk'), so baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('Search SocialFetch docs') plus the target domain ('API/SDK questions'), and immediately contrasts with the sibling docs_read. An agent can pick between them without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit routing: use docs_search for API/SDK questions, use docs_read for response fields (with its 'outline' default), and query `field crosswalk` or read the crosswalk path for cross-platform author/timestamp naming. That is when-to-use plus named alternatives with conditions.

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