Skip to main content
Glama

list_subscriptions

Retrieve a list of all active subscriptions including subscription IDs, categories, and filter conditions to manage your A2A Market subscriptions.

Instructions

列出我的所有活跃订阅。返回订阅列表含 subscription_id、品类、过滤条件。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool schema registration for 'list_subscriptions' – defines the tool name, description, and an empty inputSchema (no parameters needed).
    {
      name: 'list_subscriptions',
      description: '列出我的所有活跃订阅。返回订阅列表含 subscription_id、品类、过滤条件。',
      inputSchema: { type: 'object' as const, properties: {} },
  • Handler case within the main tool dispatch switch – calls client.listSubscriptions() with no arguments.
    case 'list_subscriptions':
      result = await client.listSubscriptions();
      break;
  • Actual API client method – sends a GET request to '/acap/v1/subscriptions' to retrieve all active subscriptions.
    async listSubscriptions() {
      return this.request('GET', '/acap/v1/subscriptions');
    }
  • src/index.ts:143-146 (registration)
    Tool is listed under the 'subscription' group in the tool organization map.
    subscription: [
      'subscribe_intent', 'unsubscribe_intent', 'list_subscriptions',
      'get_incoming_intents',
    ],
Behavior2/5

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

With no annotations, the description should communicate behavioral traits. It does not mention idempotency, authentication requirements, or that it lists only the current user's subscriptions. The read-only nature is implied but not explicit.

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?

One sentence with essential information. Concise and front-loaded, but could be slightly more structured (e.g., separate purpose and return fields).

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 0-parameter tool without output schema, the description is minimally adequate. It lists return fields but lacks context on pagination, sorting, or scope (e.g., 'active' definition). Could be more 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?

There are zero parameters, and schema coverage is 100%. The description adds meaning by listing return fields (subscription_id, category, filter criteria), which is helpful as there is no output schema.

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 clearly states the verb '列出' (list) and resource '我的所有活跃订阅' (my active subscriptions), and specifies return fields. It distinguishes from sibling list tools by narrowing to subscriptions.

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?

No explicit guidance on when to use this tool vs alternatives like list_conversations or list_matches. The description only states what it does, not when it is appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ggqshuai-hub/a2amarket-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server