twentycrm-graphql-mcp

execute_graphql

Run raw GraphQL queries or mutations on Twenty CRM to read or modify data, with optional variables for dynamic operations.

Instructions

Run any raw GraphQL query or mutation against Twenty.

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": {
      "query": "<query>"
    },
    "name": "execute_graphql"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	The GraphQL query or mutation string
`variables`	No	Optional variables for the query

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.9Aug 30, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It acknowledges that mutations can be run, but it does not warn about destructive side effects, permission requirements, rate limits, or error behavior. For a raw GraphQL execution tool, this is a significant transparency gap.

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?

The description is a single sentence with no filler or repetition. The core action is front-loaded and immediately understandable.

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?

For a powerful raw GraphQL execution tool with no annotations and no output schema, the description is too thin. It lacks guidance on when to use it, relationship to sibling tools, safety considerations, and what the agent should expect when executing arbitrary mutations.

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 query and variables parameters are already documented in the input schema. The description adds no additional parameter-level meaning or usage examples, which is acceptable given the high schema coverage.

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 states a specific verb ('Run'), a specific resource ('raw GraphQL query or mutation'), and a target system ('Twenty'). It clearly differentiates this from sibling tools like inspect_schema and execute_metadata by emphasizing raw, arbitrary GraphQL execution.

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?

The description gives no guidance about when to use this tool versus inspect_schema or execute_metadata. There is no mention of preferred use cases, exclusions, or conditions that would make another sibling more appropriate.

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

Deploy Server