Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Mastodon profile posts

mastodon_profile_posts_list
Read-onlyIdempotent

List public posts from a Mastodon profile by handle, with filters for originals, media, or pinned posts and cursor-based pagination.

Instructions

List the public posts of a Mastodon profile. Requires handle. 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": {
      "handle": "<handle>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "mastodon_profile_posts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoHashtag name without the `#`, e.g. `photography`. Letters of any script are allowed; the server folds case and accents.
limitNoItems per page, 1 to 40. Default: 20.
cursorNoPass `page.nextCursor` from the previous response to get the next page.
filterNo`all` (default) includes replies and boosts, `original` leaves them out, `media` keeps posts with media, `pinned` returns the pinned posts.
handleYesRequired. Account handle with its home server, e.g. `Gargron@mastodon.social`. A leading `acct:` or `@`, or a profile URL (`https://mastodon.social/@Gargron`, `https://mastodon.social/web/@Gargron`) is also accepted.
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds one genuinely useful behavioral fact - that only *public* posts are returned - plus cursor-based pagination. It says nothing about ordering, rate limits, or what an empty result means.

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?

Three short sentences, front-loaded with purpose before the requirement and pagination note. The parenthetical cursor remark is slightly redundant with the schema but costs little.

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?

With 8 parameters, rich annotations, and no output schema, the description is only minimally sufficient: it says a list is returned but not what a post entry looks like or whether pagination is signaled anywhere besides nextCursor. Most of the operational detail lives in the schema, which is acceptable but leaves the return shape underspecified.

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 handle, cursor, limit, filter, and tag are already fully documented, including formats and the enum meanings. The description only repeats that handle is required and hints at cursor use, adding no meaning beyond the schema.

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 posts of a Mastodon profile.' An agent can distinguish it from profile-level siblings like mastodon_profile_get or post-level ones like mastodon_posts_batch_get. It does not name any sibling explicitly, so it stops short of a 5.

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?

Usage is only implied by the resource ('posts of a profile'), plus a practical note to use the cursor when paginated. There is no explicit statement of when to prefer this over mastodon_timeline_hashtag_list or mastodon_posts_batch_get, and no exclusions or prerequisites beyond 'Requires handle'.

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