Skip to main content
Glama
Sign In
eventbrite-mcp

eventbrite-mcp

by prmichaelsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_media_upload

Retrieve details of a media upload, including status and processing state, using an upload token. Verify completion and monitor progress.

Instructions

Get Media Upload Information

Endpoint: GET /media/upload/

Returns information about a media upload, including upload status and processing state.

Authentication: Requires a valid Eventbrite API token with appropriate permissions.

Use Cases:

  • Check upload status after initiating a media upload

  • Verify media processing completion

  • Get media ID for use in events or organizers

  • Monitor upload progress

Response Fields:

  • id: Media upload ID

  • upload_token: Token for the upload

  • status: Upload status (pending, processing, complete, failed)

  • media_type: Type of media (image-event-logo, image-organizer-logo, etc)

  • url: URL of the uploaded media (when complete)

  • created: Upload creation timestamp

Error Codes:

  • 400: Invalid upload token

  • 401: Authentication required

  • 404: Media upload not found

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": {
      "upload_token": "<upload_token>"
    },
    "name": "get_media_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
upload_tokenYesThe upload token returned from a previous upload initiation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A4.1/5.0
Behavior5/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 of behavioral disclosure. It states the HTTP method and endpoint, authentication requirements, a detailed response field list with status values, and relevant error codes, giving an agent strong operational context.

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 front-loaded with the core purpose and then organized into useful sections for endpoint, authentication, use cases, response fields, and errors. It is longer than minimal, but most sections earn their place because there is no output schema.

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

Completeness5/5

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

With no output schema and no annotations, the description compensates by documenting authentication, the endpoint, response fields, status values, and error codes. An agent has enough information to invoke the tool and interpret common outcomes.

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 single upload_token parameter is already documented in the schema. The description mentions upload_token only indirectly in the response fields and error codes, adding little meaning beyond the schema's own explanation.

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: returns information about a media upload, including upload status and processing state, and gives the exact endpoint GET /media/upload/. It is clear what the tool does, but it does not explicitly differentiate itself from sibling tools such as get_media or upload_media.

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 Use Cases section gives clear contexts for calling the tool: checking upload status after initiating a media upload, verifying processing completion, getting a media ID, and monitoring progress. It does not explicitly name alternatives or state when not to use this tool.

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