affiliate-networks-mcp

affiliate_ebay_get_programme

Fetch a single eBay Partner Network programme by ID to get its commission, status, and advertiser URL. Use when you know the programme ID.

Instructions

Fetch a single programme on eBay Partner Network by its network programme id. Use this when you already know the programme id and need its full record (commission, status, advertiser URL). Returns a single Programme; pair with list_programmes when you need to discover the id first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "programmeId": "<programmeId>"
    },
    "name": "affiliate_ebay_get_programme"
  }
}

Input Schema

Name	Required	Description	Default
`programmeId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.20.0Jul 31, 2026

TDQS

A4.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the return type ('Returns a single Programme') and mentions key fields (commission, status, advertiser URL), but does not mention auth requirements, error behavior, or explicitly confirm read-only semantics. This is adequate for a simple getter but not comprehensive.

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

Conciseness5/5

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

Three concise sentences: purpose, usage context, and return value with pairing hint. Every sentence adds value, no redundancy, and the key action is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one parameter and no output schema, the description covers purpose, usage, return type, and gives examples of returned fields. It also provides navigation advice (pair with list_programmes). Missing error handling/auth details, but these are not critical for a fetch operation. Overall, it is comprehensive for the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only provides 'programmeId' as a string with no description. The description adds meaning by calling it the 'network programme id' and explaining that it identifies the programme to fetch. This compensates for the 0% schema coverage, though it doesn't specify format or validation rules.

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

Purpose5/5

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

The description clearly states the action ('Fetch a single programme'), the resource ('programme on eBay Partner Network'), and the scope ('by its network programme id'). It distinguishes itself from list_programmes, which is used for discovering ids, and from other networks by explicitly naming eBay Partner Network.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use this when the programme id is already known and you need the full record, and pairs with list_programmes for id discovery. This provides clear when-to-use guidance and names the alternative tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server