Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_set_user_tokens_with_expiry

Set eBay user access and refresh tokens with custom expiry times. Automatically refresh expired access tokens when a valid refresh token exists.

Instructions

Set user access and refresh tokens with custom expiry times. This is an enhanced version of ebay_set_user_tokens that accepts expiry times and can automatically refresh the access token if it's expired but the refresh token is valid. Useful when user provides tokens that may already be partially expired.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accessTokenYeseBay user access token
autoRefreshNoWhether to validate and refresh the access token immediately
refreshTokenYeseBay user refresh token
accessTokenExpiryNoOptional access-token expiry. Supports ISO date strings, Unix timestamps, and relative time.
refreshTokenExpiryNoOptional refresh-token expiry. Supports ISO date strings, Unix timestamps, and relative time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.14.1
    • changedInput schema / properties / accessTokenExpiry / description
      Previous value: -"Optional: Access token expiry time. If not provided, defaults to 2 hours from now. Can be ISO date string, Unix timestamp, or relative time (e.g., \"in 7200 seconds\")"New value: +"Optional access-token expiry. Supports ISO date strings, Unix timestamps, and relative time."
    • changedInput schema / properties / autoRefresh / description
      Previous value: -"If true and access token is expired but refresh token is valid, automatically refresh the access token. Default: true"New value: +"Whether to validate and refresh the access token immediately"
    • changedInput schema / properties / refreshTokenExpiry / description
      Previous value: -"Optional: Refresh token expiry time. If not provided, defaults to 18 months from now. Can be ISO date string, Unix timestamp, or relative time"New value: +"Optional refresh-token expiry. Supports ISO date strings, Unix timestamps, and relative time."
  2. First observedv1.8.10

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the auto-refresh behavior ('can automatically refresh the access token if it's expired but the refresh token is valid'). However, it does not mention potential failure scenarios, authentication requirements, or side effects. The description adds some value but lacks comprehensive behavioral detail.

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?

The description is concise with two sentences, front-loading the main purpose and quickly adding key differentiators. Every sentence provides value without unnecessary verbosity.

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?

Given the tool has 5 parameters, no output schema, and no annotations, the description explains the purpose, variant, and auto-refresh behavior. However, it does not specify the return value (e.g., success/failure) or prerequisites like needing prior authorization. It is adequate but has gaps for a complex token-setting operation.

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 baseline is 3. The description adds context about custom expiry times and auto-refresh but does not add meaning beyond the schema descriptions, which are already clear. Thus, it meets but does not exceed the baseline.

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 verb ('Set') and the resource ('user access and refresh tokens'), and distinguishes itself from the sibling 'ebay_set_user_tokens' by mentioning it is an enhanced version that accepts expiry times and can auto-refresh.

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

Usage Guidelines4/5

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

The description provides useful context by stating 'Useful when user provides tokens that may already be partially expired,' implying the scenario for using this tool over the basic version. However, it does not explicitly state when not to use it or mention other alternatives beyond the implied basic version.

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