Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Read SocialFetch docs page

docs_read
Read-onlyIdempotent

Read a documentation corpus page by its pathname from search results to retrieve API parameters, credits, and field details; use full mode to include examples and SDK snippets.

Instructions

Read a corpus page by docsPathname from docs_search. Defaults to mode=outline (compact field digest). Pass mode=full for Examples/SDK snippets. Accepts /docs/... and /product/... pathnames (including /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": {
      "docsPathname": "<docsPathname>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "docs_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNooutline (default) = compact params/credits/field digest. full = complete page including Examples.outline
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.
docsPathnameYesCorpus pathname from docs_search, e.g. /docs/api/v1/tiktok/videos/get or /product/ask-ai/field-crosswalk. Trailing .mdx accepted.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the bar is lower. The description adds real context beyond them: the compact-vs-complete default tradeoff and which pathname families are accepted, including the /product/ask-ai/field-crosswalk case. It does not discuss page size or truncation, keeping it short of a 5.

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 primary action and input source, then defaults, then constraints. No filler or redundant restatement of the title.

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?

With no output schema, the description usefully characterizes what each mode returns (compact field digest vs full page with Examples). The conversation_id sequencing rule and context/llm_model parameters are fully covered by the schema, so the remaining omission is minor.

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 coverage is 100%, so both docsPathname and mode already carry descriptions. The narrative largely restates those (default outline, full for Examples, pathname sourced from docs_search) rather than adding new syntax or format detail, so the 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 (Read) and resource (a corpus page) plus the exact addressing key (docsPathname from docs_search). This makes it immediately distinguishable from the sibling docs_search, which produces those pathnames rather than consuming them.

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

Usage Guidelines4/5

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

Gives explicit mode-selection guidance: default to outline, switch to full when Examples/SDK snippets are needed, and use pathnames from docs_search. It has clear context but no explicit exclusions or when-not-to-use 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