Skip to main content
Glama

Follow or claim a writer

get_follow_links
Read-onlyIdempotent

Links for a person who wants to keep following a Substack writer's growth, and for a writer who wants to claim their own page. Use it when the user asks to track, follow, watch or get updates on a writer (a reader, sponsor or brand), or says they are the writer. A reader gets the writer's page and a link that adds the writer to their watchlist once they confirm on the page; a writer gets a link to claim their page. Also says what the free plan and Pro include. Creates nothing: the person acts on the site.

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>"
    },
    "name": "get_follow_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesThe writer: a Substack handle (kyla or @kyla), a profile link, a publication address such as kyla.substack.com or a custom domain, or the writer's name.
audienceNoreader (default): someone who wants to follow the writer. writer: the writer, who wants to claim their page.

Output Schema

NameRequiredDescriptionDefault
nameNo
inputYes
linksYes
plansNo
handleNo
statusYes
audienceYes
suggestionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / properties / plans / properties / pro_price
      Removed value: -{
      -  "type": "string"
      -}
  2. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false. The description adds genuinely useful context that 'Creates nothing: the person acts on the site' and explains the two-step confirm-on-page flow, which clarifies the otherwise confusing gap between 'follow' and a read-only tool. It does not cover rate limits, auth, or what the returned link looks like, so it's solid but 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.

Conciseness3/5

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

The core is front-loaded and useful, but the trailing 'Also says what the free plan and Pro include' reads as a stray meta fragment that doesn't describe behavior an agent can act on. The middle sentence is dense and mixes three ideas in one run-on.

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 an output schema present, return values need no explanation, and the description covers both audience branches plus the non-mutating behavior. Only the dangling plan/Pro sentence and lack of guidance relative to get_writer leave a small gap.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds meaning to the audience enum by spelling out the distinct artifact each value produces (page + watchlist link vs. claim link) and hints at who counts as a reader (sponsor, brand). It adds little for 'handle' beyond the schema's own examples.

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 states a concrete outcome — returning links so a reader can follow a writer's growth or a writer can claim their page — and splits it by audience. It's distinguishable from a data-fetch tool like get_writer, though it never names a sibling to contrast with.

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?

Explicit trigger conditions are given: 'when the user asks to track, follow, watch or get updates on a writer... or says they are the writer.' There are no when-not conditions or named alternatives, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.