Skip to main content
Glama
Sign In
atlassian-browser-mcp

atlassian-browser-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Field Options

jira_get_field_options
Read-onlyIdempotent

Retrieve allowed option values for Jira custom fields such as select, multi-select, radio, checkbox, and cascading selects, with optional filtering and result limits.

Instructions

Get allowed option values for a custom field.

Returns the list of valid options for select, multi-select, radio, checkbox, and cascading select custom fields.

Cloud: Uses the Field Context Option API. If context_id is not provided, automatically resolves to the global context.

Server/DC: Uses createmeta to get allowedValues. Requires project_key and issue_type parameters.

Input Schema

NameRequiredDescriptionDefault
containsNoCase-insensitive substring filter on option values. Also matches child values in cascading selects.
field_idYesCustom field ID (e.g., 'customfield_10001'). Use jira_search_fields to find field IDs.
context_idNoField context ID (Cloud only). If omitted, auto-resolves to the global context.
issue_typeNoIssue type name (required for Server/DC). Example: 'Bug'
project_keyNoProject key (required for Server/DC). Example: 'PROJ'
values_onlyNoIf true, return only value strings in a compact JSON format instead of full option objects.
return_limitNoMaximum number of results to return (applied after filtering).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.4.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / return_limit / minimum
      Added value: +1
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  2. Addedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral context: Cloud resolves to the global context automatically, while Server/DC routes through createmeta and mandates project_key and issue_type. It does not disclose response shape or failure modes, keeping it below 5.

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?

It is front-loaded with the core purpose, then organized into clearly separated Cloud and Server/DC notes. Every sentence conveys operationally relevant information with no filler.

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?

With an output schema present, return-value explanation is unnecessary, and the description covers the platform-specific calling requirements an agent needs. Only minor gaps remain, such as how the 'contains' filter interacts with cascading selects, which is instead left to the schema.

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 coverage is 100%, so the baseline is 3. The description reinforces the context_id default and the platform-conditional requirement on project_key/issue_type, but adds no syntax or format detail beyond what the schema fields already state.

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 opens with a specific verb and resource ('Get allowed option values for a custom field') and enumerates the exact field types supported (select, multi-select, radio, checkbox, cascading select), which clearly distinguishes it from the sibling jira_search_fields that only finds field IDs.

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?

It specifies when the tool applies by field type and explains the Cloud vs Server/DC branching, including the required parameters for each platform. It does not name an explicit alternative or a when-not-to-use condition, so it falls short of a 5.

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

Deploy Server

Other Tools