Shippo

shippo_list_tools

Read-only

List Shippo API operations available through this server. Use this FIRST to discover what operations exist before calling shippo_describe_tool or one of the execute tools.

Returns each operation's short name, category, kind (read or write), and one-line description. Filter by category (e.g. 'Webhooks', 'Manifests', 'Address Book'), kind ('read' or 'write'), or query (natural-language keywords matched against names and descriptions). Pass no arguments to list everything.

There are ~74 operations spanning 17 categories: Addresses, Address Book, Batches, Carrier Accounts, Customs, Manifests, Orders, Parcels, Pickups, Rates, Refunds, Service Groups, Shipments, Shippo Accounts, Tracking, Transactions, Webhooks.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	No	Optional kind filter.
`query`	No	Optional natural-language search keywords.
`category`	No	Optional category filter (case-insensitive substring).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes	Number of operations matched after filtering.
`tools`	Yes	Matched operations, sorted case-insensitively by name.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 22, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Adds details beyond annotations: returns short name, category, kind, description; mentions ~74 operations and 17 categories. No contradictions.

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-loaded with purpose and usage, well-structured sentences without redundancy. Every sentence adds value.

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

Completeness5/5

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

Covers purpose, usage, filtering, output content, and scope. Output schema exists, so return format details are appropriately omitted.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All three parameters are described in schema; description adds context like case-insensitive category, natural-language query, and kind filter options.

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 explicitly states it lists Shippo API operations for discovery, with a clear verb and resource. It distinguishes from siblings by specifying it should be used first.

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?

Clear guidance to use this tool first before others, with optional filtering. Lacks explicit 'when not to use' but context is strong.

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

All Shippo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.