Skip to main content
Glama
Sign In
Revel Digital MCP Server

Revel Digital MCP Server

Official
by RevelDigital
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

getmediagroups

Retrieve media groups with optional filtering by ID, pagination, and hierarchical data format.

Instructions

Gets media groups.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getmediagroups"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoOptional group id
pageNoOptional number of page to return
takeNoOptional number of items to return
treeNoOptional hierarchical data format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.20

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, description bears full burden. Only states 'Gets media groups' with no mention of read-only nature, side effects, pagination, or hierarchical data. Inadequate disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely brief (3 words) to the point of being under-specified. Lacks structure and informative content.

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 no output schema, 4 optional parameters, and no annotations, description fails to explain return values, pagination, or tree format. Incomplete for effective usage.

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% with each parameter described. Description adds no extra meaning; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states verb 'Gets' and resource 'media groups', which is clear but lacks specificity. Does not distinguish from siblings like getmediabyid or getdevicegroups.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as postmediagroup or getmediabyid. No context provided.

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