Skip to main content
Glama

Save a standing query

subscribe

Be notified of future posts matching a query (same fields as search). Give a webhook_url to be pushed to, or poll with check_subscription. Needs an api_key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "subscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoA name for this subscription, for your own reference.
queryYesSame fields as search, minus limit/cursor/sort.
api_keyNoPublisher API key (crier_sk_...). Optional if the MCP connection sends an Authorization header.
webhook_urlNoOptional https URL to POST matches to (HMAC-signed).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / properties / include_expired / description
      Previous value: -"'true' to include posts whose expires_at has passed."New value: +"'true' to include posts whose expires_at has passed, and posts their publisher closed."
  2. Changed2 schema fields changed
    • changedInput schema / properties / query / properties / after / description
      Previous value: -"ISO 8601; only posts whose window ends at/after this (or created after, if no window)."New value: +"ISO 8601 date (midnight UTC) or date-time with an offset, e.g. 2026-09-12 or 2026-09-12T21:00:00-05:00; only posts whose window ends at/after this (or created after, if no window)."
    • changedInput schema / properties / query / properties / before / description
      Previous value: -"ISO 8601; only posts whose window starts at/before this."New value: +"ISO 8601 date (midnight UTC) or date-time with an offset, e.g. 2026-09-14 or 2026-09-14T00:00:00-05:00; only posts whose window starts at/before this."
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It discloses future-notification behavior, push vs poll delivery, and auth needs, but omits return shape, subscription lifecycle, duplicate handling, and webhook signing details. 'Needs an api_key' also slightly overstates the schema's optional-if-header behavior.

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?

Two short sentences, front-loaded with the core behavior and followed by delivery and auth details. There is no wasted wording.

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?

It covers the essential call mechanics and alternatives, but for a subscription-creation tool with no output schema it does not explain what is returned or how the created subscription is later referenced. The nested query schema is fully documented, reducing the need to repeat field details.

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%, so the schema already documents all four parameters and the nested query object. The description adds that query uses the same fields as search and that webhook_url is for push delivery, but its api_key statement conflicts with the schema's caveat that it is optional when an Authorization header is sent.

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 states a specific outcome: being notified of future posts matching a query. It distinguishes this from search by emphasizing future posts and from polling via check_subscription.

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 gives a clear delivery choice: provide webhook_url for push or poll with check_subscription. It also states the api_key requirement, but does not explicitly say when not to use this versus search for existing posts.

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.