agentView

Manage Display Category

manage_display_category

Destructive

Creates or renames a display category (categories group displays for broadcast_content include_category_ids). action 'create' needs name (optional parent_category_id for a subcategory); action 'rename' needs category_id and new_name — assignments and grants stay intact. Discover IDs with list_display_categories; assign displays with assign_display_categories.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Category name for action 'create', e.g. 'Reception'.
`action`	Yes	Operation to perform.
`new_name`	No	New category name (rename only).
`category_id`	No	Category ID to rename (rename only).
`access_token`	No	Optional bearer token; prefer session_request_id.
`parent_category_id`	No	Optional parent category ID (create only) for a subcategory.
`session_request_id`	No	Session handle from create_auth_session; pass it on every authenticated call.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No
`path`	No
`oldPath`	No
`categoryId`	No
`parentCategoryId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 1, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "categoryId": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "oldPath": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "parentCategoryId": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "path": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

AddedJul 6, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already communicate mutation and destructive potential, so the description adds useful context by stating that assignments and grants stay intact on rename. This explains a behavioral consequence beyond what the schema or annotations alone convey, though it doesn't elaborate on all potential side effects.

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

Conciseness5/5

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

Two sentences carry substantial, well-organized information: action options, parameter requirements, behavioral note, and pointers to sibling tools. There is no filler and the key distinctions are front-loaded.

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?

Given the 100% schema coverage, output schema availability, and annotations, the description is complete enough for an agent to call the tool correctly. It covers the action-dependent requirements and points to the sibling tools for ID discovery and assignment, leaving no significant functional gap.

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 description coverage is 100%, so each parameter is already documented individually. The description adds action-conditional meaning, specifying which parameters apply to create versus rename and that parent_category_id is create-only, which helps the agent assemble the correct call.

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

Purpose5/5

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

The description uses a specific verb phrase, 'Creates or renames a display category,' and defines the domain concept by noting categories group displays for broadcast_content include_category_ids. This clearly differentiates it from sibling tools like list_display_categories and assign_display_categories.

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

Usage Guidelines5/5

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

It explicitly maps each action to its required parameters ('create' needs name; 'rename' needs category_id and new_name), and directs the agent to sibling tools for related tasks: list_display_categories for discovering IDs and assign_display_categories for assigning displays. This is strong when-to-use guidance.

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

All agentView 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.

Resources

Need Help?