AIVA MCP Server

aiva_list_subscriptions

Retrieve and filter subscription data from Shopify stores to manage active, paused, or cancelled subscriptions with product-based filtering.

Instructions

List subscriptions with filters.

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

Input Schema

Name	Required	Description	Default
`status`	No		active
`productId`	No	Filter by product
`limit`	No
`offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jan 24, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'with filters' but doesn't cover critical aspects like whether this is a read-only operation, pagination behavior (implied by limit/offset but not explained), rate limits, or authentication needs. The description is minimal and leaves key behaviors unspecified.

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?

The description is very concise with a single sentence, 'List subscriptions with filters.', which is front-loaded and wastes no words. However, it may be overly terse given the tool's complexity, potentially sacrificing clarity for brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain the return format, error handling, or how filters interact, leaving significant gaps for an AI agent to understand and invoke the tool correctly in context.

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 description coverage is low at 25%, with only the 'status' parameter having an enum description. The description adds no specific meaning beyond 'with filters', which is already implied by the parameters in the schema. It doesn't explain parameter interactions or usage, so it marginally compensates but doesn't fully address the coverage gap.

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

Purpose3/5

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

The description 'List subscriptions with filters' clearly states the action (list) and resource (subscriptions), but it's vague about scope and doesn't differentiate from sibling tools like 'aiva_get_subscription' (singular) or 'aiva_subscription_actions'. It specifies 'with filters' which adds some context but remains general.

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 guidance is provided on when to use this tool versus alternatives such as 'aiva_get_subscription' for a single subscription or 'aiva_search_customers' for broader queries. The description implies usage for filtered listing but lacks explicit context or exclusions.

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

Deploy Server