Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_get_negative_keywords

Retrieve negative keywords from eBay Marketing API to exclude unwanted search terms from your campaigns.

Instructions

Get negative keywords through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNolimit optional endpoint parameter
offsetNooffset optional endpoint parameter
adGroupIdsNoadGroupIds optional endpoint parameter
campaignIdsNocampaignIds optional endpoint parameter
negativeKeywordStatusNonegativeKeywordStatus optional endpoint parameter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.14.1
    • changedInput schema / properties / adGroupIds / description
      Previous value: -"Comma-separated list of ad group IDs to filter by."New value: +"adGroupIds optional endpoint parameter"
    • changedInput schema / properties / campaignIds / description
      Previous value: -"Filter by campaign ID (only one campaign ID is supported per request)."New value: +"campaignIds optional endpoint parameter"
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return"New value: +"limit optional endpoint parameter"
    • changedInput schema / properties / negativeKeywordStatus / description
      Previous value: -"Comma-separated list of negative keyword statuses to filter by."New value: +"negativeKeywordStatus optional endpoint parameter"
    • changedInput schema / properties / offset / description
      Previous value: -"Number of results to skip"New value: +"offset optional endpoint parameter"
  2. Addedv1.12.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are present, so the description must fully convey behavioral traits. It only states 'Get' which implies a read operation but provides no details on pagination, result format, or dependencies. This is insufficient for a read tool with multiple parameters.

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 sentence with no wasted words, which is concise. However, it is overly brief and lacks structure to convey additional important information.

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?

Given the tool has 5 optional parameters and no output schema, the description should explain what the tool returns and how to use the filters. It only states the basic purpose, leaving the agent with inadequate context for effective use.

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%, but each parameter description (e.g., 'limit optional endpoint parameter') adds no meaning beyond the schema itself. The tool description offers no additional value, so the baseline score of 3 applies.

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 specifies the verb 'Get' and the resource 'negative keywords', making the purpose clear. However, it does not differentiate from the sibling tool 'ebay_get_negative_keyword' (singular), which is only implied by the plural in the name.

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 guidelines are provided on when to use this tool versus alternatives like 'ebay_get_negative_keyword' or filtering by status, campaign, etc. The description lacks context for usage.

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