Skip to main content
Glama
freema

mcp-jira-stdio

by freema
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

jira_get_my_issues

Read-only

Retrieve Jira issues assigned to you, sorted by most recent updates. Supports pagination and custom field selection for efficient results.

Instructions

Retrieves issues assigned to current user, sorted by most recently updated first. Supports pagination and field selection. For pagination, use nextPageToken from previous response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
expandNoAdditional details to include
fieldsNoSpecific fields to retrieve
maxResultsNoMaximum number of results to return per page
nextPageTokenNoToken for pagination. Omit for first page, use value from previous response for next page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.11.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed9 schema fields changedv1.10.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / expand / default
      Removed value: -[]
    • changedInput schema / properties / expand / description
      Previous value: -"Additional details to include for each issue"New value: +"Additional details to include"
    • changedInput schema / properties / fields / description
      Previous value: -"Specific fields to retrieve for each issue"New value: +"Specific fields to retrieve"
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of results to return"New value: +"Maximum number of results to return per page"
    • addedInput schema / properties / nextPageToken
      Added value: +{
+  "description": "Token for pagination. Omit for first page, use value from previous response for next page.",
+  "type": "string"
+}
    • removedInput schema / properties / startAt
      Removed value: -{
-  "default": 0,
-  "description": "Index of first result to return (for pagination)",
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / required
      Removed value: -[]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, confirming the tool is read-only. The description adds behavioral details like sorting by recency and pagination support (nextPageToken). No contradictions.

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?

Two sentences, front-loaded with the core purpose. Every sentence adds essential information: first sentence covers main function and sorting, second covers pagination. No waste.

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?

Given no output schema, the description covers sorting, pagination, and field selection. It lacks mention of the return structure (list of issues with fields), but the pagination token hints at the response format. Reasonably complete for a read-only tool with good annotations.

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 the baseline is 3. The description adds value by explicitly stating how to use nextPageToken for pagination ('use from previous response'), which is not fully captured in schema descriptions.

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 retrieves issues assigned to the current user, sorted by most recent update, and supports pagination and field selection. This distinguishes it from siblings like jira_search_issues (arbitrary search) and jira_get_issue (single issue).

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

Usage Guidelines3/5

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

The description provides basic context (user's own issues, sorted by update) but lacks explicit guidance on when to use versus alternatives. It does not mention exclusions or contrast with search or get_issue, leaving the agent to infer usage.

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