Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Mastodon trending posts

mastodon_trends_posts_list
Read-onlyIdempotent

Fetch trending posts from a chosen Mastodon server to identify active conversations and topics, with pagination for browsing results.

Instructions

List the posts trending on 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_trends_posts_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.
cursorNoPass `page.nextCursor` from the previous response (a plain number is taken as an offset). The list is ordered live, so a row can appear on two pages; remove repeats by `id`, `name` or `url`.
offsetNoItems to skip, as an offset. Prefer `cursor` for the next page. Default: 0.
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

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 the safety profile is covered. The description adds only the host requirement and a cursor hint; it says nothing about the live-ordering duplicate risk or the conversation_id sequencing constraint that the schema documents.

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?

Two short sentences, front-loaded with the purpose, with zero redundant wording.

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 seven-parameter tool with three required meta-parameters, the description covers the core action and pagination but omits the conversation_id sequencing rule and the analytics-only nature of context/llm_model. No output schema exists, so the brief 'Returns a list' is adequate but thin.

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 seven parameters are already documented in detail. The description merely restates that host is required and that cursor is used for pagination, 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 posts trending on a Mastodon server.' The word 'posts' implicitly separates it from the hashtag and link trending siblings, though no sibling is named explicitly.

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?

Adds a pagination hint ('use cursor when paginated') and notes the host requirement, but gives no guidance on when to choose this over mastodon_trends_hashtags_list or mastodon_trends_links_list, nor any exclusions.

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