Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Mastodon server custom emoji

mastodon_server_emojis_list
Read-onlyIdempotent

List a Mastodon server's custom emojis by host, with cursor-based paging for large sets. Use it to discover available emoji shortcodes before composing posts or rendering content.

Instructions

List the custom emoji 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_server_emojis_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 1000. Default: 200.
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.
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, open-world behavior, so the safety profile is covered elsewhere. The description adds the host-required constraint and a pagination hint, but omits return shape details, rate limits, or pagination termination behavior for what is an open-world network call.

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, front-loaded sentences with no filler; the resource is named first and operational notes follow. It is efficient but nearly all of its content duplicates the schema.

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 fully documented six-parameter read tool with no output schema, the description leaves the return value as just "a list" without noting what emoji entries contain or whether the list is capped. Adequate to call the tool, but thin given the absence of an output schema.

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 coverage is 100%, so all six parameters, including the host, limit, and cursor semantics, are already documented in the schema. The description only restates that host is required and that cursor applies when paginated, which is marginal added meaning beyond the schema's own cursor explanation.

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 gives a specific verb and resource ("List the custom emoji of a Mastodon server"), which is distinguishable from the many timeline/profile/trend siblings. It does not explicitly contrast itself with nearby server-scoped tools such as mastodon_server_get, but the purpose is unambiguous.

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 states the host prerequisite and the cursor usage for pagination, so basic invocation context is present. It gives no when-to-use/when-not guidance relative to alternatives and says nothing about rate limits or who can call it.

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