Skip to main content
Glama

Set project field

set_project_field
Destructive

Add a column to a project, or edit the one that already has this name. Keyed by name rather than by id: 'make sure there is a Segment field with these options' is the request, and a name is what you just read. A field's KIND cannot be changed once it exists. Project lead or admin only.

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": {
      "projectKey": "<projectKey>",
      "name": "<name>"
    },
    "name": "set_project_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoThe glyph that mark wears, from the palette list_project_fields returns. Not for a country field: that one marks a card with the flag of the country the issue holds, so passing an icon is refused rather than ignored.
kindNoWhat it holds: 'text', 'number', 'date' (a day), 'datetime' (a day and a time, written like 2026-10-01T19:30+03:00), 'user', 'select' (a list), 'country' (a country, written as its name or its two-letter code and shown with a flag) or 'link' (issues and wiki pages, one or several — what a row is confirmed by). Required when creating; ignored when the field already exists, since a kind cannot change.
nameYesField name, e.g. 'Segment'. An existing field with this name is edited rather than duplicated.
newNameNoRename the field to this. Leave out to keep the name.
optionsNoFor a list: its options, as 'AI:green, Skins:orange, GameCards' or a JSON array of {name, color}. A colour is optional and must be one of: orange, amber, red, pink, purple, blue, teal, green. Options left out are REMOVED — send the whole set.
showIconNoMark a board card when this field has a value: true to switch the mark on, false off. Leave out to keep it as it is.
issueTypeNoKeep the field for issues of one type only, by name — e.g. 'Показ' — or '' for every type. Leave out to keep it as it is. Superseded by issueTypes, which wins when both are given.
issueTypesNoKeep the field for issues of these types only, by name: 'Epic, Story' or a JSON array ["Epic","Story"]. '' or [] for every type. The whole set — types left out are removed. Leave out to keep it as it is.
projectKeyYesProject key, e.g. 'CRM'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / issueType / description
      Previous value: -"Keep the field for issues of one type only, by name — e.g. 'Показ' — or '' for every type. Leave out to keep it as it is."New value: +"Keep the field for issues of one type only, by name — e.g. 'Показ' — or '' for every type. Leave out to keep it as it is. Superseded by issueTypes, which wins when both are given."
    • addedInput schema / properties / issueTypes
      Added value: +{
      +  "default": null,
      +  "description": "Keep the field for issues of these types only, by name: 'Epic, Story' or a JSON array [\"Epic\",\"Story\"]. '' or [] for every type. The whole set — types left out are removed. Leave out to keep it as it is.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / kind / description
      Previous value: -"What it holds: 'text', 'number', 'date' (a day), 'datetime' (a day and a time, written like 2026-10-01T19:30+03:00), 'user', 'select' (a list) or 'country' (a country, written as its name or its two-letter code and shown with a flag). Required when creating; ignored when the field already exists, since a kind cannot change."New value: +"What it holds: 'text', 'number', 'date' (a day), 'datetime' (a day and a time, written like 2026-10-01T19:30+03:00), 'user', 'select' (a list), 'country' (a country, written as its name or its two-letter code and shown with a flag) or 'link' (issues and wiki pages, one or several — what a row is confirmed by). Required when creating; ignored when the field already exists, since a kind cannot change."
  3. Changed2 schema fields changed
    • addedInput schema / properties / issueType
      Added value: +{
      +  "default": null,
      +  "description": "Keep the field for issues of one type only, by name — e.g. 'Показ' — or '' for every type. Leave out to keep it as it is.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedInput schema / properties / kind / description
      Previous value: -"What it holds: 'text', 'number', 'date', 'user', 'select' (a list) or 'country' (a country, written as its name or its two-letter code and shown with a flag). Required when creating; ignored when the field already exists, since a kind cannot change."New value: +"What it holds: 'text', 'number', 'date' (a day), 'datetime' (a day and a time, written like 2026-10-01T19:30+03:00), 'user', 'select' (a list) or 'country' (a country, written as its name or its two-letter code and shown with a flag). Required when creating; ignored when the field already exists, since a kind cannot change."
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the description's job is to add context, and it does: it discloses the permission gate (lead or admin), the upsert/no-duplicate behavior, and the irreversible constraint that a field's kind cannot change once created. It does not itself warn that omitted options wipe existing ones — that risk statement lives only in the schema.

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?

Three short sentences, front-loaded with the add-or-edit contract, then the name-keying rationale, then the immutability warning. The aside 'and a name is what you just read' is slightly conversational but earns its place by explaining why the tool is name-keyed.

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?

For a destructive, nine-parameter tool with no output schema, the description covers the essentials: upsert semantics, the auth requirement, and the one hard invariant (kind is immutable). Remaining gaps — return shape, and what happens to values when options shrink — are handled inside the parameter descriptions.

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 schema already carries parameter meaning, including the editing-by-name behavior and the kind-immutability rule the description restates. The description's 'keyed by name rather than by id' framing adds a little interpretive context but largely duplicates what 'name' and 'kind' already document.

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 opening sentence gives a precise verb pair and resource: 'Add a column to a project, or edit the one that already has this name,' which pins down the upsert semantics an agent needs. It never names the adjacent tools (list_project_fields, delete_project_field), so the differentiation from siblings is implied by behavior rather than stated.

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?

'make sure there is a Segment field with these options' is the request' frames the intended idempotent ensure-style usage clearly, and 'Project lead or admin only' gives a hard prerequisite. It stops short of telling the agent when to prefer delete_project_field or to consult list_project_fields first for existing icons/options.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources