Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_suggest_bids

Retrieve bid suggestions for active listings in an eBay campaign ad group to set competitive auction bids and improve advertising ROI.

Instructions

Suggest bids through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesSuggest bids request body
adGroupIdYesadGroupId required endpoint parameter
campaignIdYescampaignId required endpoint parameter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.14.1
    • changedInput schema / properties / adGroupId / description
      Previous value: -"Ad Group ID"New value: +"adGroupId required endpoint parameter"
    • changedInput schema / properties / campaignId / description
      Previous value: -"Campaign ID"New value: +"campaignId required endpoint parameter"
    • addedInput schema / properties / request
      Added value: +{
+  "additionalProperties": false,
+  "description": "Suggest bids request body",
+  "properties": {
+    "bid": {
+      "additionalProperties": false,
+      "properties": {
+        "currency": {
+          "type": "string"
+        },
+        "value": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "listingId": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • changedInput schema / required
      Previous value: -[
-  "campaignId",
-  "adGroupId"
-]New value: +[
+  "adGroupId",
+  "campaignId",
+  "request"
+]
  2. First observedv1.8.10

TDQS

C2.5/5.0
Behavior2/5

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

The annotation readOnlyHint=false indicates this is not a read-only operation, but the description doesn't clarify what side effects occur. It doesn't state whether this creates, updates, or merely calculates suggested bids, whether it modifies campaign state, or what the response contains. With no output schema and minimal description, the agent lacks critical behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise, but it's under-specified. It front-loads the verb and resource but provides no additional context. The sentence is not wasteful, but it doesn't earn its place beyond restating the tool name.

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 tool with 3 required parameters, a nested request object, no output schema, and a non-read-only annotation, the description is incomplete. It doesn't explain what the suggestion is based on, what the response format is, or how the bid value in the request relates to the suggestion. An agent would need to consult external API documentation to use this correctly.

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 the schema documents all three parameters. The description adds no additional meaning beyond the schema. The nested 'request' object with 'bid' and 'listingId' is self-explanatory from the schema, but the description doesn't clarify the relationship between bid suggestions and the provided bid value, which could be ambiguous.

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

Purpose3/5

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

The description states a specific verb and resource ('Suggest bids through the eBay Marketing API'), which is clear enough to identify the operation. However, it doesn't distinguish this from closely related siblings like ebay_suggest_budget, ebay_suggest_items, ebay_suggest_keywords, or ebay_suggest_max_cpc, all of which share the same 'suggest' pattern. The name itself carries most of the meaning.

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 provided on when to use this tool versus alternatives. The description doesn't mention that this is for bid suggestions in advertising campaigns, nor does it explain the relationship to ebay_suggest_max_cpc or ebay_update_bid. An agent would have to infer usage from the parameter names (adGroupId, campaignId) and the sibling tool names.

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