Skip to main content
Glama

invoke_ai_action

Invoke a Contentful AI Action with custom variables. Provide the action ID, space, and environment, and receive generated content in Markdown, RichText, or PlainText format.

Instructions

Invoke an AI Action with variables

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aiActionIdYesThe ID of the AI Action to invoke
variablesNoKey-value pairs of variable IDs and their values
rawVariablesNoArray of raw variable objects (for complex variable types like references)
outputFormatNoThe format of the output contentMarkdown
waitForCompletionNoWhether to wait for the AI Action to complete before returning
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?

The description does not disclose behavioral traits such as whether the invocation blocks, alters state, or requires special permissions. No annotations are provided to supplement this, so the description carries the full burden but fails to deliver.

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 a single sentence and front-loaded, but it is too concise to convey sufficient meaning, bordering on under-specification.

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 (7 parameters, 3 required, nested objects) and no output schema, the description is incomplete. It fails to explain return values, error conditions, or the behavior of key parameters like waitForCompletion.

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 description coverage is 100%, so the baseline is 3. The description adds minimal value beyond the schema, only mentioning 'variables' in a generic way.

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 'Invoke' and the resource 'AI Action with variables', distinguishing it from sibling tools like get_ai_action, list_ai_actions, etc. However, it lacks specificity on what invoking an AI Action entails.

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 is provided on when to use this tool versus alternatives such as get_ai_action or list_ai_actions. The description does not mention prerequisites or typical use cases.

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