Skip to main content
Glama

ebay_create_negative_keyword

Create a negative keyword in eBay campaigns to block unwanted search terms and prevent ads from showing for irrelevant queries. Specify match type and keyword text to refine ad targeting.

Instructions

Create negative keyword through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesCreate negative keyword request body

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.14.1
    • removedInput schema / properties / adGroupId
      Removed value: -{
      -  "description": "Ad Group ID",
      -  "type": "string"
      -}
    • removedInput schema / properties / campaignId
      Removed value: -{
      -  "description": "Campaign ID",
      -  "type": "string"
      -}
    • removedInput schema / properties / negativeKeywordMatchType
      Removed value: -{
      -  "description": "Match type (broad matching is not supported for negative keywords).",
      -  "enum": [
      -    "EXACT",
      -    "PHRASE"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / negativeKeywordText
      Removed value: -{
      -  "description": "The negative keyword text.",
      -  "type": "string"
      -}
    • addedInput schema / properties / request
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Create negative keyword request body",
      +  "properties": {
      +    "adGroupId": {
      +      "type": "string"
      +    },
      +    "campaignId": {
      +      "type": "string"
      +    },
      +    "negativeKeywordMatchType": {
      +      "type": "string"
      +    },
      +    "negativeKeywordText": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "negativeKeywordMatchType",
      +    "negativeKeywordText"
      +  ],
      +  "type": "object"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "negativeKeywordText",
      -  "negativeKeywordMatchType"
      -]New value: +[
      +  "request"
      +]
  2. Addedv1.12.0

TDQS

C2.9/5.0
Behavior2/5

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

The description only restates the mutation ('Create') and names the API, adding no behavioral context beyond the readOnlyHint: false annotation. It does not mention effects, required identifiers, idempotency, or response behavior, so the description carries little beyond what the name and annotations already imply.

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 short sentence with no wasted words. It is concise, though its brevity comes at the cost of useful context.

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 nested-object create operation with no output schema and no parameter explanations, the description is underspecified. An agent cannot determine how adGroupId and campaignId relate to the negative keyword, what match types are valid, or what a successful response looks like.

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 already documents the request object and required fields. However, the description adds no meaning to negativeKeywordMatchType, negativeKeywordText, adGroupId, or campaignId, leaving their semantic roles to the property names.

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 states a specific verb and resource: 'Create negative keyword' via the eBay Marketing API. It is clear enough to know this creates a single negative keyword, though it does not explicitly distinguish itself from sibling ebay_bulk_create_negative_keyword or ebay_create_keyword.

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?

There is no guidance about when to use this tool instead of alternatives like ebay_bulk_create_negative_keyword, ebay_get_negative_keywords, or ebay_update_negative_keyword. The intended use must be inferred entirely from the tool name and one-line description.

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