Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Substack profile

substack_profile_get
Read-onlyIdempotent

Fetch a Substack reader's public profile and subscription list by handle to identify their interests and followed publications.

Instructions

Get a Substack reader's public profile and subscriptions. Requires handle.

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": {
      "handle": "<handle>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "substack_profile_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesRequired. A profile handle, e.g. `dieworkwear` or `@dieworkwear`.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only 'public profile', hinting at visibility limits, but says nothing about failure modes for private or missing handles, rate limits, or auth needs.

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

Conciseness4/5

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

Two short sentences with the operation front-loaded and no filler. It is efficient, though the second sentence mostly repeats the schema's 'Required' note on `handle` rather than contributing new information.

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?

For a simple read-only lookup with no output schema, the description is minimally adequate but leaves the agent guessing what the response contains and how it differs from the dedicated subscriptions sibling. Given the openWorld hint and cross-platform profile ecosystem, a sentence on scope would have closed the gap.

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 all four parameters, including `context` and `llm_model`, are already documented in the schema. The description singles out `handle` as required but adds no new semantics; baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource: 'Get a Substack reader's public profile and subscriptions.' An agent knows this retrieves a profile, though 'and subscriptions' overlaps with the sibling substack_profile_subscriptions_list, leaving slight ambiguity about which payload is authoritative.

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?

The only guidance is 'Requires `handle`', which restates a required parameter rather than explaining when to call this versus substack_profile_posts_list, substack_profile_notes_list, or substack_profile_subscriptions_list. No exclusions or alternative-selection logic is offered.

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