Retrieve available Oracle Cloud media services, including transcoding and live or VOD streaming options, to identify the services you need for your streaming setup.
[DEPRECATED: use list_services_by_category with category="media"] List OCI Media Services including Media Flow (transcoding) and Media Streams (live/VOD streaming).
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Filter by media service type |
Changes observed during successful MCP inspections.
v1.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds deprecation status, which is important behavioral context beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no wasted words; deprecation is front-loaded, and the purpose is stated concisely.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool is deprecated and has only one optional parameter, the description covers the essential context: deprecation, alternative, and purpose. No output schema but reading hints are in annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for the single parameter 'type', so the description does not need to add parameter info. Baseline 3 is appropriate as no additional semantics are provided.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it lists OCI Media Services with specific types (Media Flow and Media Streams), and the deprecation note provides an alternative. The purpose is precise and distinguishes from sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly recommends using list_services_by_category with category='media' instead, clearly indicating when not to use this tool and providing the alternative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.