Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Mastodon server public timeline

mastodon_timeline_public_list
Read-onlyIdempotent

List a Mastodon server's public timeline by host with local, remote, or media-only filters; use cursor pagination to retrieve additional posts.

Instructions

List the public timeline of a Mastodon server. Requires host. Returns a list (use cursor when paginated).

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

Input Schema

NameRequiredDescriptionDefault
hostYesRequired. The Mastodon server to ask, e.g. `mastodon.social`. A server URL is also accepted. The server you name is the one that answers.
limitNoItems per page, 1 to 40. Default: 20.
scopeNo`all` (default) is everything the server has seen, `local` only the server's own accounts, `remote` only accounts from other servers.
cursorNoPass `page.nextCursor` from the previous response to get the next page.
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.
mediaOnlyNoOnly posts with media attachments.
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds the host requirement and pagination behavior, but says nothing about rate limits, result ordering, or the required conversational handshake implied by conversation_id/context/llm_model in the schema.

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 prerequisite front-loaded and the return/pagination note second; nothing is wasted. The parenthetical about cursor is slightly compressed but functional, so it falls just short of exemplary.

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 and eight parameters (three required, one enum), the schema carries the parameter burden and the annotations carry the safety profile, leaving the description to state scope and pagination, which it does. The main gap is that it never mentions the scope/mediaOnly filtering options an agent might want to surface.

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 including scope, mediaOnly, limit and cursor is already documented in the schema. The description only restates the `host` requirement and cursor usage, adding no syntax or default details beyond the structured fields. Baseline 3 applies.

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: 'List the public timeline of a Mastodon server.' An agent can tell it is a public-timeline read, distinct from profile or hashtag timelines by name. It does not, however, explicitly contrast itself with siblings such as mastodon_timeline_hashtag_list or mastodon_trends_posts_list.

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

Usage Guidelines3/5

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

It gives a hard prerequisite ('Requires `host`') and a pagination cue ('use cursor when paginated'), which are actionable. But there is no when-to-use guidance relative to the hashtag timeline, trends, or directory tools, and no note on when the scope/mediaOnly filters should be chosen.

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