Panda Video

Provision Team User

panda_action_provision_user

Create a team user, resolving the role by name (or original_name/ID) to its role_id (POST /users). dry_run=true (default) previews. Validates the email format up front.

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": {
      "name": "<name>",
      "email": "<email>",
      "role_ref": "<role_ref>"
    },
    "name": "panda_action_provision_user"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	User's display name
`email`	Yes	User email
`phone`	No	Optional phone number
`dry_run`	No	true = preview only; false = create
`role_ref`	Yes	Role name or ID (e.g. 'viewer', 'editor')
`idempotency_key`	No	Reserved client-supplied retry key

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), and the description adds genuinely non-obvious behavior: the create is a no-op preview by default, the role reference is resolved to a role_id server-side, and the email is validated before the call. It omits retry/idempotency behavior despite exposing an idempotency_key.

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?

Three compact sentences, front-loaded with the create action and its key default. Slightly telegraphic ('resolving the role by name ... to its role_id', 'Validates the email format up front') but every sentence carries information.

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 mutating, non-annotated-for-branding tool with no output schema, the description covers the create semantics and the preview default, but leaves gaps: no success/error shape, no note on the idempotency_key, and no disambiguation from panda_create_user. Adequate but incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by explaining that role_ref accepts a role name (or original_name/ID) that gets resolved to a role_id, and by calling out the dry_run default semantics. It says nothing about idempotency_key, which the schema only labels as 'reserved'.

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 and resource ('Create a team user') plus the underlying endpoint (POST /users) and the role-resolution behavior. It is clear what the tool does, but it never distinguishes itself from the sibling panda_create_user, which an agent could easily confuse it with.

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?

The dry_run default is surfaced ('dry_run=true (default) previews'), which implies a safe preview-first workflow, but there is no explicit when-to-use guidance and no mention of when to prefer this over panda_create_user or panda_update_user. Usage is implied rather than stated.

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

All Panda Video tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.