Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_update_ad_rate_strategy

Update eBay ad rate strategy for a campaign via Marketing API. Set campaignId and request body with adRateStrategy to adjust bidding.

Instructions

Update ad rate strategy through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesUpdate ad rate strategy request body
campaignIdYescampaignId required endpoint parameter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.14.1
    • changedInput schema / properties / campaignId / description
      Previous value: -"Campaign ID"New value: +"campaignId required endpoint parameter"
    • addedInput schema / properties / request
      Added value: +{
+  "additionalProperties": false,
+  "description": "Update ad rate strategy request body",
+  "properties": {
+    "adRateStrategy": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • removedInput schema / properties / strategy
      Removed value: -{
-  "additionalProperties": false,
-  "description": "Ad rate strategy",
-  "properties": {
-    "bidPercentage": {
-      "description": "New bid percentage (e.g., \"10.5\")",
-      "type": "string"
-    }
-  },
-  "required": [
-    "bidPercentage"
-  ],
-  "type": "object"
-}
    • changedInput schema / required
      Previous value: -[
-  "campaignId",
-  "strategy"
-]New value: +[
+  "campaignId",
+  "request"
+]
  2. First observedv1.8.10

TDQS

C2.9/5.0
Behavior2/5

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

Annotations only indicate readOnlyHint=false, so the description carries the burden of behavioral disclosure. It simply says 'Update' with no mention of side effects, reversibility, rate limits, or requirements. This is minimal and does not enrich the agent's understanding of the operation's impact.

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 a single concise sentence with no fluff, front-loading the action and resource. It is appropriately sized but arguably too sparse; however, conciseness is a strength here, so a 4 is warranted.

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 write operation with a nested object and no output schema, the description is incomplete. It does not explain what ad rate strategy values are valid, what the update does, or any prerequisites. An agent lacks critical context to correctly invoke this tool.

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%, so both parameters are documented in the schema. The description adds no additional meaning about parameters, such as accepted values for adRateStrategy or constraints on campaignId. Baseline 3 is appropriate since the schema covers the basics.

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 the resource ('ad rate strategy'), which is specific and distinct from siblings like ebay_update_bidding_strategy. However, it does not explicitly differentiate itself from other update tools beyond the resource name, so it lacks explicit sibling differentiation.

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 given on when to use this tool versus alternatives, nor are there any prerequisites or conditions mentioned. The description only states what it does, not when to invoke it.

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

Deploy Server

Other Tools