Skip to main content
Glama

List social formats

list_formats
Read-only

The social formats the studio renders to, with exact export pixel sizes and platforms.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_formats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe, side-effect-free read. The description adds useful behavioral context that isn't in the annotations: the result includes exact export pixel sizes and platform associations. It does not say whether the list is static/curated or configurable, which is the remaining gap; a 3 fits given annotations carry the safety profile.

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 no filler; the resource and the two payload attributes (pixel sizes, platforms) come first. It is a sentence fragment, which slightly undercuts clarity but wastes nothing.

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 zero-parameter, read-only listing with no output schema, the description does the one thing that matters: it characterizes what comes back (formats with exact export pixel sizes and platforms). Nothing an agent needs to invoke it correctly is missing, though a note on whether the set is fixed would make it fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning the description needs to supply. The description instead spends its words on the return content, which is the right allocation for a zero-arg tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource ('the social formats the studio renders to') and its payload (pixel sizes and platforms), so an agent can infer it returns a reference list of export formats. However it is a noun-phrase fragment with no verb, and mentioning 'platforms' in the payload risks confusion with the sibling list_platforms, which the description does not address.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use statement, no exclusion, and no pointer to an alternative such as list_platforms or list_marketing_presets. The agent must infer from the name alone that this is the reference lookup for choosing an export target.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources