Skip to main content
Glama

ebay_get_campaign_by_name

Retrieve detailed information about an eBay marketing campaign by providing its exact name, enabling quick access to campaign settings and performance data.

Instructions

Find a campaign by its name. Returns campaign details if a matching name is found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignNameYesCampaign name to search for
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It only states that it returns campaign details if found, but does not mention what happens if no match exists, whether it's read-only, or any side effects. The lack of output schema also leaves the agent ignorant of the return structure.

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?

Two short sentences convey the essential purpose with no redundant information. Every word is necessary.

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

Completeness3/5

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

For a simple lookup tool, the description is adequate but incomplete. It does not clarify whether the name is unique or what 'campaign details' includes. The absence of an output schema makes the description insufficient for an agent to fully understand the return value.

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?

The schema provides 100% coverage with a description for campaignName. The description adds no further meaning beyond what is already in the schema, so it meets the baseline for high schema coverage.

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 specifies the action (find) and resource (campaign by name). It distinguishes from siblings like ebay_get_campaign (likely by ID) and ebay_get_campaigns (lists all), making the purpose unambiguous.

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 guidance on when to use this tool versus alternatives such as ebay_get_campaign (by ID) or ebay_find_campaign_by_ad_reference. The description does not clarify when the name-based lookup is appropriate or when it might fail.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/YosefHayim/ebay-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server