Skip to main content
Glama

twprojects-update_custom_item_record

Update specific fields on a custom item record. Only supplied values are changed; others remain intact. Clear a field by sending null. Use to modify Contracts, Leads, or any custom entity.

Instructions

Update a record on a custom item type. Only the fields you supply are changed; others are left as-is. Set section_id to null to remove the record from any section. Custom items are user-defined entity types — Contracts, Leads, Deals, or anything else a customer has set up on a project. Use these tools when the user refers to an entity that is NOT a built-in Teamwork concept (Task, Tasklist, Project, Milestone, Comment, Notebook, Company, Team, User, Tag). If you don't recognise an entity name in the user's request, assume it is a custom item and call twprojects-list_custom_items on the relevant project to confirm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clear_sectionNoSet to true to explicitly clear the record's section. Use this instead of section_id when you want null semantics.
custom_item_idYesCustom item type ID the record belongs to.
field_valuesNoField values to set on the record. Each entry is {field_name, value}. Field names are matched case-insensitively against the custom item type's fields. Values are coerced by field type: dropdown/multiselect accept option labels or option twIds; date/time/datetime accept ISO-8601 strings; checkbox accepts bool or yes/no/true/false; number accepts numeric or numeric string; user accepts a user ID (or array of IDs for multi-user fields). To clear a field, send null.
idYesRecord ID to update.
nameNoNew display name for the record.
position_after_idNoMove the record after the given record ID.
section_idNoNew section ID, or null to remove the record from any section.
Behavior5/5

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

No annotations beyond title, so description carries full burden. It discloses partial update behavior, null section removal, and field value coercion rules. No contradictions with annotations.

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?

Single paragraph that is well-focused and front-loaded with purpose and key behavior. Could be slightly more structured, but not verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but update tool return is usually standard. Description covers partial update, null semantics, and field coercion. Adequate for a complex custom item 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 coverage is 100%, baseline 3. The description adds value by explaining the clear_section vs section_id distinction and field coercion details not fully in schema. Slight redundancy but overall adds meaning.

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 clearly states the tool updates a record on a custom item type, and explains that custom items are user-defined entity types. It distinguishes itself from siblings that update built-in entities.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use this tool versus others: when the entity is not a built-in Teamwork concept. Also advises to call list_custom_items on the project to confirm if unsure, and notes that only supplied fields are changed.

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/Teamwork/mcp'

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