Skip to main content
Glama

subscribe_intent

Subscribe to buyer intents for specific categories with optional budget and region filters. Receive notifications for matches, then use associated tools to view and respond with quotes.

Instructions

订阅特定品类的买家意图。有匹配意图时收到通知。用 get_incoming_intents 查看匹配到的意图,用 respond_to_intent 报价。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
category_l1Yes一级品类(必填)
category_l2No二级品类
min_budgetNo最低预算过滤
max_budgetNo最高预算过滤
regionsNo地区过滤

Implementation Reference

  • The tool handler for subscribe_intent: parses input via SubscribeIntentSchema and calls the client's subscribeIntent method.
    case 'subscribe_intent': {
      const p = S.SubscribeIntentSchema.parse(args);
      result = await client.subscribeIntent(p);
      break;
  • Zod schema for subscribe_intent input validation. category_l1 is required; category_l2, min_budget, max_budget, and regions are optional.
    export const SubscribeIntentSchema = z.object({
      category_l1: z.string().min(1, 'category_l1 为必填项'),
      category_l2: z.string().optional(),
      min_budget: z.number().nonnegative().optional(),
      max_budget: z.number().positive().optional(),
      regions: z.string().optional(),
    });
  • src/index.ts:594-609 (registration)
    Tool registration entry for subscribe_intent in the tools array, defining its name, description, and input JSON schema.
    // ═══ 卖家 — 意图订阅 ═══
    {
      name: 'subscribe_intent',
      description: '订阅特定品类的买家意图。有匹配意图时收到通知。用 get_incoming_intents 查看匹配到的意图,用 respond_to_intent 报价。',
      inputSchema: {
        type: 'object' as const,
        properties: {
          category_l1: { type: 'string', description: '一级品类(必填)' },
          category_l2: { type: 'string', description: '二级品类' },
          min_budget: { type: 'number', description: '最低预算过滤' },
          max_budget: { type: 'number', description: '最高预算过滤' },
          regions: { type: 'string', description: '地区过滤' },
        },
        required: ['category_l1'],
      },
    },
  • Client helper method that sends a POST request to /acap/v1/subscriptions with the subscription criteria.
    async subscribeIntent(criteria: {
      category_l1?: string; category_l2?: string;
      min_budget?: number; max_budget?: number;
      regions?: string; notify_channel?: string;
    }) {
      return this.request('POST', '/acap/v1/subscriptions', criteria);
    }
  • src/index.ts:143-146 (registration)
    Tool grouped under 'subscription' category in the tool grouping configuration.
    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?

No annotations exist, so the description must carry the full burden. It mentions notifications on match but lacks details on whether the subscription persists, requires specific permissions, or has rate limits. It also doesn't disclose if it's a write operation or its side effects.

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?

Three sentences, no wasted words. The first sentence states the core purpose, followed by the notification aspect and references to related tools. Efficient and front-loaded.

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?

Given the tool's simple nature (subscribe with filters) and the presence of sibling tools for related actions, the description covers the essential flow. However, it omits details like return value (success/failure), subscription lifetime, and how to manage subscriptions (unsubscribe intent exists but not mentioned). Adequate but not thorough.

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% with parameter descriptions, so baseline is 3. The description adds minimal value beyond the schema: it mentions 'categories' (category_l1) but doesn't elaborate on budget or region filters. It does not provide additional semantics or examples.

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

Purpose5/5

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

The description clearly states the action (subscribe to intents), the resource (buyer intents for specific categories), and the outcome (receive notifications). It also distinguishes from sibling tools by referencing get_incoming_intents and respond_to_intent for subsequent actions.

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

Usage Guidelines4/5

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

It explicitly tells when to use the tool (to subscribe to intents) and provides a clear workflow (use get_incoming_intents to view matches, respond_to_intent to quote). However, it does not mention when not to use it or alternative approaches, which would make it a 5.

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