Bulk update ad statuses in a campaign using the eBay Marketing API.
Bulk update ads status through the eBay Marketing API.
| Name | Required | Description | Default |
|---|---|---|---|
| request | Yes | Bulk update ads status request body | |
| campaignId | Yes | campaignId required endpoint parameter |
Changes observed during successful MCP inspections.
v1.14.1Input schema / properties / adsRemoved value: -{
- "additionalProperties": false,
- "description": "Bulk status update request",
- "properties": {
- "requests": {
- "description": "Array of status update requests",
- "items": {
- "additionalProperties": false,
- "properties": {
- "adId": {
- "description": "Ad ID",
- "type": "string"
- },
- "adStatus": {
- "description": "New ad status",
- "enum": [
- "ACTIVE",
- "PAUSED",
- "ARCHIVED"
- ],
- "type": "string"
- }
- },
- "required": [
- "adId",
- "adStatus"
- ],
- "type": "object"
- },
- "type": "array"
- }
- },
- "required": [
- "requests"
- ],
- "type": "object"
-}Input schema / properties / campaignId / descriptionPrevious value: -"Campaign ID"New value: +"campaignId required endpoint parameter"Input schema / properties / requestAdded value: +{
+ "additionalProperties": false,
+ "description": "Bulk update ads status request body",
+ "properties": {
+ "requests": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "adStatus": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "adStatus"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+}Input schema / requiredPrevious value: -[
- "campaignId",
- "ads"
-]New value: +[
+ "campaignId",
+ "request"
+]v1.8.10Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description only says 'bulk update ads status' without detailing behavioral traits like idempotency, side effects, or error handling.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence is under-specified and insufficient; lacks necessary detail for correct usage.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given complexity (nested object, many siblings, no output schema, no annotations), description is completely inadequate for an agent to use correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for both parameters, but description adds no additional meaning beyond what's in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description states 'Bulk update ads status' which is a specific verb+resource, but doesn't distinguish from sibling tools like ebay_bulk_update_ads_status_by_listing_id. Lacks scope clarity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. No prerequisites or context provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.