Grigora

update_directory_item

Destructive

Update a directory item.

Args: project_id: The project ID. collection_id: The collection ID. item_id: The item ID. name: New name (leave empty to keep current). slug: New slug (leave empty to keep current). fields: JSON object of field values to update (leave empty to keep current).

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": {
      "project_id": "<project_id>",
      "collection_id": "<collection_id>",
      "item_id": "<item_id>"
    },
    "name": "update_directory_item"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`slug`	No
`fields`	No
`item_id`	Yes
`project_id`	Yes
`collection_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a mutation. The description adds genuine behavioral detail by explaining the partial-update semantics ('leave empty to keep current') for name, slug, and fields, but never acknowledges the destructive nature or reversibility that the annotation implies.

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-loads the one-line purpose and then a compact Args list; no filler prose. Minor waste in restating ids as 'The project ID' etc., but overall tight and scannable.

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?

With an output schema present, return values needn't be explained, and annotations carry the safety profile, so the remaining burden is modest. The missing piece is usage context and sibling differentiation, leaving the definition adequate but not complete for a destructive mutation tool.

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 0%, so the description must carry the load, and it does: all six parameters are documented with meaning beyond their titles, and the partial-update rule ('leave empty to keep current') plus 'JSON object of field values' adds real semantics. The three id params are still largely tautological restatements.

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 clear verb+resource ("Update a directory item") that an agent can distinguish from update_directory_collection and update_directory_field by resource. It does not, however, further scope what a 'directory item' is or what fields are editable beyond the param list.

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?

There is no when-to-use guidance, no mention of alternatives (e.g. update_directory_collection/field), and no prerequisites such as required permissions. The description is purely a parameter dump with no routing context.

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

All Grigora 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?