eventbrite-mcp

list_organization_roles

Retrieve paginated roles and permissions for a specific Eventbrite organization by ID to inspect or manage access levels.

Instructions

List Roles by Organization.

ENDPOINT: GET /organizations/{organization_id}/roles/

Organization Role represents set of permissions owned by Organization.

Returns paginated response.

AUTHENTICATION: Requires: Authorization: Bearer PERSONAL_OAUTH_TOKEN

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": {
      "organization_id": "<organization_id>"
    },
    "name": "list_organization_roles"
  }
}

Input Schema

Name	Required	Description	Default
`organization_id`	Yes	Organization ID (required)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.6Sep 13, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose two behavioral traits beyond the schema: the response is paginated and the call requires Authorization: Bearer PERSONAL_OAUTH_TOKEN. It does not state read-only safety explicitly, but 'List' plus the auth disclosure covers the essentials a caller needs.

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?

Front-loaded with the purpose, then structured ENDPOINT and AUTHENTICATION blocks that are easy to scan. The definitional line about what a Role represents is useful rather than filler, though the formatting is slightly verbose for a one-parameter tool.

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?

No output schema exists, so the description's note that the response is paginated does useful work, and auth is covered. For a simple one-required-param list tool, nothing essential is missing.

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% and the single parameter is already documented as 'Organization ID (required)'. The description adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb+resource ('List Roles by Organization') and even names the underlying endpoint GET /organizations/{organization_id}/roles/. It defines what an Organization Role is, so an agent understands the entity. Sibling listing tools (list_organization_members, list_organizations) aren't explicitly contrasted, so it stops short of a 5.

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?

Usage is implied by the verb 'List' and the required organization_id, but there is no explicit when-to-use guidance or routing to alternatives such as list_organization_members. Adequate but leaves the agent to infer context.

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

Deploy Server