Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Mastodon profiles by id

mastodon_profiles_batch_get
Read-onlyIdempotent

Retrieve up to 40 Mastodon profiles by account IDs from a chosen server, returning a list for batch profile lookups.

Instructions

Get up to 40 Mastodon profiles by their ids. Requires host and ids. Returns a list.

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>",
      "ids": "<ids>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "mastodon_profiles_batch_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesRequired. Comma-separated account ids on `host`, 1 to 40. Ids belong to that server.
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.
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 fully covered. The description adds only the batch ceiling and 'Returns a list', saying nothing about partial results, missing ids, or per-host resolution — useful but thin beyond the structured data.

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 the capability and the 40-item cap before the requirement restatement. The 'Requires host and ids' and 'Returns a list' sentences are near-redundant with the schema, costing a point.

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?

For a simple read-only batch lookup with full schema coverage and complete annotations, the description covers the essential scope and limit. No output schema exists, yet 'Returns a list' is enough for an agent to know the shape is a collection.

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 host, ids, context, llm_model and conversation_id are all documented in the schema. The description merely restates that host and ids are required and echoes the 1–40 bound; it adds no meaning about id formats or host normalization.

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 specific verb and resource ('Get ... Mastodon profiles') and adds batch scope ('up to 40 ... by their ids'), which distinguishes it from the singular mastodon_profile_get sibling. 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 word 'batch' and the 40-id cap; there is no statement of when to prefer this over mastodon_profile_get or what to do if ids span multiple servers. An agent can infer the batch case but receives no explicit routing rule or 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