Skip to main content
Glama

List capabilities

capabilities
Read-onlyIdempotent

What can be called now. With platform: each action and op there, with parameters, credits, page size, fields it cannot give and a call that works. Without: only the platforms and how many calls each has. Free. Platforms now: bilibili, douyin, facebook, google, instagram, kuaishou, linkedin, meta, pinterest, reddit, telegram, threads, tiktok, wechat, wechat_channels, weibo, x, xiaohongshu, youtube, zhihu.

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": "capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNoThis platform's calls.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / platform / description
      Previous value: -"Only this platform."New value: +"This platform's calls."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses cost ("Free"), that output shape varies by argument, and that the detailed mode includes parameters, credits, page size, unsupported fields, and a working example call. That is meaningful behavioral context the annotations do not carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key behavior is front-loaded and there is no filler, but the telegraphic sentence fragments ("Free.", "With platform: ...") read as compressed notes rather than prose, and the trailing list of 20 platforms takes up roughly half the text.

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?

With no output schema, the description does a reasonable job of describing both return modes and introduces the platform values. Gaps remain on error handling for an invalid platform and on the pagination/size behavior hinted at by "page size".

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 schema only says "This platform's calls"; the description explains the concrete consequence of supplying it (per-action detail for that platform) versus omitting it (platform names plus call counts). It also supplies the platform vocabulary the schema lacks (no enum), though it does not say what happens with an unknown platform.

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?

"What can be called now" states a specific discovery purpose (a catalog of invocable actions) and the with/without-platform branching makes the resource concrete. It never names the closest sibling (call) or explains how this differs from it, so differentiation is left to inference.

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 description implicitly tells the agent to pass a platform for full action-level detail and omit it for a cheap overview, and "Free" signals no cost barrier. It gives no explicit when-to-use vs. siblings like call/find, nor when not to call it.

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.