Skip to main content
Glama

List my migrations

list_my_migrations
Read-onlyIdempotent

List the customer's email migrations across all states (in-progress, scheduled, complete, cancelled). Use when the user asks "what migrations do I have?", "is my migration done?", "what's the status of my email move?", or to find the migrationId to pass to get_migration_status. Read-only; starting, confirming or cancelling a migration happens in the Squish dashboard.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of migrations to return (default 10, max 25).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description reinforces read-only and adds the genuinely useful boundary that mutation actions live only in the dashboard. It does not describe what a returned record looks like (status field, scheduled date, ordering), which is the main remaining behavioral gap given there is no output schema.

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?

Front-loads the core action and scope in the first clause, then supplies routing cues and an exclusion in a second sentence. The example utterances are dense but each one maps to a distinct real user phrasing, so no sentence is padding.

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

Completeness4/5

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

For a one-parameter, read-only list tool with no output schema, the description covers purpose, triggers, sibling routing, and mutation boundaries adequately. The only shortfall is that it never hints at the returned fields or ordering, which would help an agent chain into get_migration_status reliably.

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% and the single 'limit' parameter is fully documented in-schema with default 10 and max 25. The description adds no additional meaning about 'limit' (e.g., ordering, paging beyond the cap), so the baseline 3 applies.

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?

States a specific verb and resource ('List the customer's email migrations') plus the scope ('across all states (in-progress, scheduled, complete, cancelled)'). It also implicitly differentiates itself from get_migration_status by framing itself as the enumeration step whose output feeds that tool.

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

Usage Guidelines5/5

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

Gives concrete trigger phrasings ('what migrations do I have?', 'is my migration done?') and names the downstream alternative with the exact condition that selects it ('to find the migrationId to pass to get_migration_status'). It also states an out-of-scope boundary: starting, confirming or cancelling happens in the Squish dashboard, not via this tool.

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.

Resources