Skip to main content
Glama

ebay_get_seller_standards_profile

Retrieve a seller's standards profile for a given program and cycle to evaluate performance and compliance status.

Instructions

Get a specific seller standards profile

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cycleYesSeller standards cycle, e.g., CURRENT or PROJECTED
programYesSeller standards program identifier
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'Get a specific seller standards profile' with no mention of side effects, authentication needs, rate limits, or response contents. This is minimal behavioral disclosure.

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 sentence of 5 words, which is extremely concise. However, it is somewhat under-specified for a tool with no output schema, so it earns a 4 rather than a 5.

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 that there is no output schema, the description should explain what the profile contains. It does not. Additionally, with many sibling tools, some usage context would help the agent decide when to use this tool. The description is incomplete for effective tool selection.

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 coverage is 100% (both parameters have descriptions in the schema). The description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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 specifies 'Get a specific seller standards profile'. The verb 'Get' and resource 'seller standards profile' are clear. It distinguishes from the sibling tool 'ebay_find_seller_standards_profiles' by emphasizing 'specific' versus searching or listing.

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

Usage Guidelines3/5

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

No when-to-use or when-not-to-use guidance is provided. The description implies use when you have the required identifiers (program, cycle), but it does not mention alternatives or exclusions. The sibling 'find' tool is not referenced.

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