Skip to main content
Glama

vivid-ads-commerce

vivid_fulfilment_shipping

Read-onlyIdempotent

StarShipit shipping: carrier, tracking number, tracking URL, ETA and delivered flag. shipping_state: not_dispatched, shipped, in_transit, out_for_delivery, delivered, exception.

Input Schema

NameRequiredDescriptionDefault
tokenNoidentity token from vivid_identity_verify — REQUIRED to see any details. Without it a 6-digit code is emailed to customer_email and the tool returns need_verification.
order_idNoShopify order GID, e.g. gid://shopify/Order/123.
order_nameNoHuman order name, e.g. "#12345" (alias for order_id).
line_item_idNoOptional Shopify line item GID to scope to one item.
customer_emailYesThe email address on the order. REQUIRED for identity — order details are only returned when this email matches the order. The customer must give their email AND one of their order numbers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / token
      Added value: +{
      +  "description": "identity token from vivid_identity_verify — REQUIRED to see any details. Without it a 6-digit code is emailed to customer_email and the tool returns need_verification.",
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds useful behavioral context by enumerating the shipping_state lifecycle values, but discloses nothing about auth flow, rate limits, or failure modes beyond what annotations and schema already provide.

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?

Two tight sentences with no filler, front-loading the returned fields before the state enum. It is efficient, though the fragment style lacks an explicit action clause that would orient the agent faster.

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?

There is no output schema, so the description's enumeration of return fields (carrier, tracking number, tracking URL, ETA, delivered flag, shipping_state) usefully compensates by telling the agent what comes back. For a read-only tool with a rich schema, it is largely complete, missing only sibling routing guidance.

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 100% and each parameter (token, order_id, order_name, line_item_id, customer_email) is thoroughly documented in the schema, including the identity requirements. The description adds no additional parameter meaning, so the baseline of 3 applies.

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

Purpose4/5

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

The description names the specific resource (StarShipit shipping) and enumerates the returned data points (carrier, tracking number, tracking URL, ETA, delivered flag, shipping_state), making the retrieval intent clear. It does not differentiate from the many sibling status tools (vivid_fulfilment_order_status, vivid_fulfilment_pickup_status, vivid_fulfilment_production_stage), and it omits an explicit verb, so it stops short of a 5.

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?

The description offers no when-to-use guidance, no prerequisites, and no reference to alternative tools even though the sibling list contains several closely related fulfilment-status tools. The only usage-relevant information (token required to see details, email must match) lives entirely in the schema, not the description.

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