list_subscriptionsList the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel.
| Name | Required | Description | Default |
|---|---|---|---|
| include_inactive | No | Include cancelled subscriptions in the response (default false). |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by specifying the default active filter, the returned fields, and the optional include_inactive parameter, providing sufficient behavioral context beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two efficient sentences: the first states purpose and return data, the second provides usage guidance. No wasted words, well front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool with one optional param, the description covers purpose, return fields, default behavior, and usage context. No output schema exists, but return fields are explicitly listed, making it self-contained.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with a clear description for the only parameter (include_inactive). The description does not add further parameter details, but the schema already provides adequate meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
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 'subscriptions', specifying 'active' to distinguish from inactive. It also lists fields returned, and the tool is distinct from siblings like subscribe and unsubscribe.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states when to use: 'before adding more' or 'to find an id to cancel'. This guides the agent away from using subscribe or unsubscribe when a list is needed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
There is meaningful overlap among the ask_pipeworx, deep_research, validate_claim, and polymarket_* tools, but the descriptions do draw fairly clear boundaries between them. The five yt_* tools are distinct and easy to tell apart, though the unrelated Pipeworx cluster makes the overall set feel muddier than it should.
Most tools use readable snake_case, and there are coherent prefixes like yt_ and polymarket_, but the set mixes bare verbs (remember, recall, forget, subscribe), noun-style names (entity_profile, deep_research), and API-like names (ask_pipeworx, generate_llms_txt). The pattern is not chaotic, but it is inconsistent across the set.
36 tools is well above the typical well-scoped range, and the vast majority are unrelated to the server's stated 'Youtube' identity. The actual YouTube surface is only five tools, while 31 tools belong to a different Pipeworx/Polymarket domain.
For a YouTube-focused server, the yt_* tools cover search, channel info, video details, and comments, but miss obvious surfaces like playlists, transcripts, subscriptions, uploads, and video updates. The large non-YouTube tool collection does not fill these gaps; it only makes the server feel mis-scoped.