Skip to main content
Glama

update_shipping_profile

Modify an existing Etsy shipping profile by updating costs, processing times, origin country, or title for a specific shop and profile ID.

Instructions

Update an existing shipping profile

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "shop_id": "<shop_id>",
      "shipping_profile_id": "<shipping_profile_id>"
    },
    "name": "update_shipping_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoProfile title
shop_idYesThe shop ID
primary_costNoPrimary shipping cost
secondary_costNoAdditional item cost
origin_country_isoNoOrigin country ISO code
max_processing_daysNoMax processing days
min_processing_daysNoMin processing days
shipping_profile_idYesThe shipping profile ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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. While 'Update' implies a mutation operation, the description doesn't disclose what permissions are required, whether the update is reversible, what happens to unspecified fields, rate limits, or error conditions. This is inadequate for a mutation tool with zero annotation coverage.

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?

The description is a single, efficient sentence with zero wasted words. It's appropriately sized for a basic tool description and gets straight to the point without unnecessary elaboration.

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?

For a mutation tool with 8 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the tool returns, what validation occurs, error handling, or how it relates to other shipping operations. The description should provide more context given the tool's complexity and lack of structured metadata.

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?

The schema has 100% description coverage, so all parameters are documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema. According to the scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 clearly states the action ('Update') and target resource ('an existing shipping profile'), providing a specific verb+resource combination. However, it doesn't differentiate this tool from sibling tools like 'update_listing', 'update_shop', or 'update_receipt' beyond the resource type.

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 provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (like authentication), when to use 'create_shipping_profile' instead, or how this relates to other shipping-related tools like 'get_shipping_profiles' or 'manage_shipping_destinations'.

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