Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Mastodon profile

mastodon_profile_get
Read-onlyIdempotent

Fetches a Mastodon account's public profile by handle and returns discoverability and indexing flags; use it to verify how an account can be found and indexed.

Instructions

Get a Mastodon account's public profile by handle, with the owner's discoverability and indexing flags. Requires handle.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
includeNo`featuredTags` also returns the hashtags the account features.
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 state readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds that only the public profile is fetched and that discoverability/indexing flags are part of the result, but says nothing about failure modes for unknown or remote handles, rate limits, or the shape of the response.

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?

A single front-loaded sentence with the core action first and the returned flags second; nothing is redundant. It is slightly under-specified rather than verbose, which the length does not fix.

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 single-lookup with full annotation coverage, the description gives the necessary scope plus a hint at returned fields. Without an output schema, a fuller sketch of the profile fields would be ideal, but the essentials are present.

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 baseline is 3. The description only repeats that `handle` is required — information already in the schema — and does not mention the `include=featuredTags` option that changes the returned payload.

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?

Names a specific verb and resource ("Get a Mastodon account's public profile by handle") and characterizes the payload as including discoverability and indexing flags. It is clearly a single-account lookup, but it never distinguishes itself from the sibling mastodon_profiles_batch_get or states that this is the single-handle path.

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: the reader infers this is the tool for one known handle, and the sibling batch variant is not mentioned as an alternative. No explicit when-to-use or when-not-to-use statement appears.

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