Skip to main content
Glama

Get External Issue

get_external_issue
Read-only

Fetch external issue or task details by provider IDs or keys previously linked to TestDino, such as Jira keys or Linear issue identifiers.

Instructions

Fetch external issue/task details by provider IDs or keys previously linked to TestDino, such as Jira keys TD-17 or Linear issue identifiers.

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": {
      "projectId": "<projectId>",
      "provider": "<provider>",
      "issueIds": "<issueIds>"
    },
    "name": "get_external_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNoProvider-specific target/context values. For Jira, pass { defaultApp } to read from a specific Atlassian site/resource.
issueIdsYesExternal issue IDs or keys (at most 20).
providerYesProvider to read issues from. monday.com and GitHub have no issue read route.
projectIdYesTestDino project ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.2.3
    • changedInput schema / properties / issueIds / description
      Previous value: -"External issue IDs or keys."New value: +"External issue IDs or keys (at most 20)."
    • addedInput schema / properties / issueIds / maxItems
      Added value: +20
  2. Changed8 schema fields changedv2.2.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / issueIds / description
      Previous value: -"External issue IDs or keys (Required). Array of one or more IDs previously linked to TestDino (e.g. Jira keys like 'TD-17' or Linear identifiers)."New value: +"External issue IDs or keys."
    • changedInput schema / properties / projectId / description
      Previous value: -"Project ID (Required). The TestDino project identifier."New value: +"TestDino project ID"
    • changedInput schema / properties / provider / description
      Previous value: -"Integration provider the issue lives in (Required). Use the same provider passed to create_external_issue."New value: +"Provider to read issues from. monday.com and GitHub have no issue read route."
    • changedInput schema / properties / provider / enum
      Previous value: -[
      -  "jira",
      -  "linear",
      -  "asana",
      -  "monday",
      -  "github"
      -]New value: +[
      +  "jira",
      +  "linear",
      +  "asana"
      +]
    • changedInput schema / properties / target / additionalProperties
      Previous value: -trueNew value: +{}
    • changedInput schema / properties / target / description
      Previous value: -"Provider-specific read context (optional). For Jira, pass { defaultApp } to read from a specific Atlassian site/resource."New value: +"Provider-specific target/context values. For Jira, pass { defaultApp } to read from a specific Atlassian site/resource."
  3. Addedv2.0.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile of this outward-facing read is covered. The description adds only the 'previously linked' precondition and key-format examples; it says nothing about behavior when an ID is unlinked or unknown, whether results are returned in requested order, or partial-failure handling across a batch of up to 20.

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?

A single sentence with the verb and resource front-loaded and no filler. The linked-precondition clause is doing real work rather than padding.

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?

With no output schema, the description should say something about what 'details' comprise, since callers cannot see the return shape. It also leaves the batch semantics of issueIds (up to 20) and the meaning of failure for individual IDs unaddressed, which matters for a multi-ID, provider-varying fetch.

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 provider, projectId, issueIds, and the Jira target object are all documented in the schema itself. The description contributes example key shapes ('TD-17', Linear identifiers), which is modest added value but not beyond what the schema already conveys about provider-specific targets.

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 description gives a specific verb ('Fetch') and a specific resource ('external issue/task details'), and adds the constraint that issues must already be linked to TestDino, which separates it from the write-side sibling create_external_issue. It stops short of naming that sibling or any read alternatives, so differentiation is implied rather than explicit.

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?

Usage is only implied: the phrase 'previously linked to TestDino' hints that this is for retrieving issues that already exist in the workspace, not creating or syncing them. There is no explicit statement of when to prefer this tool, nor what to do when an issue has not been linked yet.

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