Skip to main content
Glama

update_ai_action

Update an existing AI Action in Contentful by modifying its name, description, instruction template with variables, model configuration, and test cases within a specified space and environment.

Instructions

Update an existing AI Action

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aiActionIdYesThe ID of the AI Action to update
nameYesThe name of the AI Action
descriptionYesThe description of the AI Action
instructionYesThe instruction object containing the template and variables
configurationYesThe model configuration
testCasesNoOptional array of test cases for the AI Action
spaceIdYesThe ID of the Contentful space. This must be the space's ID, not its name, ask for this ID if it's unclear.
environmentIdYesThe ID of the environment within the space, by default this will be called Mastermaster
Behavior2/5

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

With no annotations, the description only says 'Update', leaving unclear whether it's a partial or full update, or what side effects occur on omitted fields.

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

Conciseness3/5

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

The description is very short (one sentence), but it's too minimal to provide useful information beyond the function name.

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 the tool's complexity (8 params, nested objects, no output schema), the description omits crucial details like update behavior, error cases, or return value.

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% and already provides detailed parameter descriptions. The tool description adds no additional semantic value beyond what the schema offers.

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?

The description clearly states the verb 'Update' and resource 'existing AI Action', distinguishing it from create and delete siblings. However, it lacks additional context about the tool's specific role.

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 like create_ai_action or delete_ai_action. No prerequisites or conditions are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ivo-toby/contentful-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server