Skip to main content
Glama

motion_custom_fields

Create, list, delete custom field definitions for tasks and projects, and assign or remove them to specific tasks and projects.

Instructions

Manage custom fields for tasks and projects. Required params per operation: list: workspaceId or workspaceName. create: workspaceId/workspaceName + name + field (type); options[] also required for select/multiSelect. delete: workspaceId/workspaceName + fieldId. add_to_project: projectId + fieldId. remove_from_project: projectId + valueId. add_to_task: taskId + fieldId. remove_from_task: taskId + valueId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesOperation to perform
fieldIdNoCustom field definition ID. Required for: delete, add_to_project, add_to_task. For remove operations, use valueId instead.
valueIdNoCustom field value assignment ID (not the field definition ID). Required for: remove_from_project, remove_from_task.
workspaceIdNoWorkspace ID. Required for: list, create, delete.
workspaceNameNoWorkspace name (alternative to workspaceId). Required for: list, create, delete.
nameNoField name. Required for: create.
fieldNoField type. Required for: create. Also needed for add_to_project/add_to_task when providing a non-null value.
optionsNoOption labels. Required for: create when field is select or multiSelect.
requiredNoWhether field is required on tasks/projects.
projectIdNoProject ID. Required for: add_to_project, remove_from_project.
taskIdNoTask ID. Required for: add_to_task, remove_from_task.
valueNoField value to set. Optional for add_to_project/add_to_task. When provided and non-null, the field param (type) is also required.
Behavior2/5

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

No annotations provided. Description does not disclose side effects, permissions, idempotency, or error conditions for operations like create, delete, add/remove. For a mutation-heavy tool, this is insufficient.

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?

Single sentence with clear structure: purpose then required params per operation. No wasted words. Highly efficient.

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?

Given 12 parameters and no output schema or annotations, the description covers operation-specific parameter requirements well but lacks behavioral context (e.g., mutation effects, auth, limits). Incomplete for a tool with many operations.

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 coverage is 100%, so baseline is 3. Description adds value by grouping required params per operation, making it easier for the agent to select correct parameters. Does not add deeper semantics beyond what schema provides.

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?

Description clearly states 'Manage custom fields for tasks and projects' which is a specific verb+resource. It distinguishes from sibling tools like motion_tasks and motion_projects by focusing on custom field management.

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

Usage Guidelines4/5

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

Explicitly lists required parameters per operation (list, create, delete, etc.), guiding the agent on when to use each operation based on available parameters. However, no mention of when not to use or alternatives.

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/markobullrush/motion-mcp-2'

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