Skip to main content
Glama

List platforms

list_platforms
Read-only

Where a campaign can go live: each placement's image and video formats (in order of preference), duration and size limits, and whether it takes a cover or caption files.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds useful return-content context—formats ordered by preference, duration and size limits, and cover/caption support—which exceeds the annotation. It does not discuss permissions, rate limits, or pagination, but for a simple read-only catalog tool that is a minor gap.

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?

A single front-loaded sentence packs all essential details with no redundant phrasing; every clause contributes to describing the result set.

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?

With no output schema and no parameters, the description carries the burden of explaining the result set, and it does so by naming the key fields and ordering. A minor gap is that it does not state the response container or whether all platforms are included, but it is otherwise sufficient.

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?

There are no input parameters, so the baseline is 4; the description correctly focuses on what the tool returns rather than misrepresenting any parameter semantics.

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 names the resource concept ('where a campaign can go live') and specifies per-placement metadata, so the agent understands it returns platform/placement options. It stops short of explicitly distinguishing itself from sibling format-list tools, but the scope is clear enough to identify the tool's purpose.

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?

The opening phrase implies the tool is for discovering campaign destinations, but there is no explicit when-to-use guidance, prerequisites, or named alternative. For a zero-parameter list tool the implied context is adequate, but clear usage guidance is absent.

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