Retrieve ad groups for an eBay marketing campaign by campaign ID, with optional status filtering and pagination.
Get ad groups through the eBay Marketing API.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | limit optional endpoint parameter | |
| offset | No | offset optional endpoint parameter | |
| campaignId | Yes | campaignId required endpoint parameter | |
| adGroupStatus | No | adGroupStatus optional endpoint parameter |
Changes observed during successful MCP inspections.
v1.14.1Input schema / properties / adGroupStatusAdded value: +{
+ "description": "adGroupStatus optional endpoint parameter",
+ "type": "string"
+}Input schema / properties / campaignId / descriptionPrevious value: -"Campaign ID"New value: +"campaignId required endpoint parameter"Input schema / properties / limit / descriptionPrevious value: -"Maximum number of results to return"New value: +"limit optional endpoint parameter"Input schema / properties / offset / descriptionPrevious value: -"Number of results to skip"New value: +"offset optional endpoint parameter"v1.8.10Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already covers the main behavioral trait, and the description's 'Get' is consistent with it. However, the description adds no further behavioral context, such as campaign scoping, pagination behavior, or default adGroupStatus filtering. It provides essentially no value beyond what the annotation already states.
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?
The description is a single concise sentence with no redundant phrasing or unnecessary length. 'Through the eBay Marketing API' is somewhat redundant given the ebay_ prefix, but the overall structure is clean and front-loaded.
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?
With no output schema, the description should explain what a caller receives and any meaningful response characteristics, but it does neither. It also omits the relationship between ad groups and the required campaignId and leaves adGroupStatus filter values unspecified. The tool is minimally callable but not fully understandable.
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?
The input schema describes all four parameters with 100% coverage, so the description does not need to restate them. The description adds no additional parameter-level guidance, such as how limit and offset interact or what adGroupStatus values are accepted, but the schema already documents names and requiredness. Baseline 3 is appropriate.
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?
The description uses a specific verb ('Get') and resource ('ad groups') and identifies the eBay Marketing API, so the basic operation is clear. It does not explicitly differentiate this list operation from sibling tools like ebay_get_ad_group or ebay_get_ads; the plural noun is the main distinguishing signal.
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?
There is no guidance on when to use this tool versus ebay_get_ad_group, ebay_get_ads, or the create/update ad-group sibling tools. No use case, prerequisite, or exclusion is described, so an agent must infer the tool's role from its name and parameters.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.