get_issue

Read the description and metadata of one known issue. Every call targets one authorized repository and leaves its issues unchanged.

Parameters

Example call

get_issue({
  "repo": "acme/sdk",
  "issue_number": 412
})

Example response

{
  "repo": "acme/sdk",
  "issue": {
    "number": 412,
    "title": "Retry loop continues after cancellation",
    "state": "open",
    "labels": [
      "bug"
    ],
    "milestone": "v2.0",
    "description": "Cancelling a request stops the active connection, but a scheduled retry still runs. The client should cancel pending retries when the request is aborted.",
    "url": "https://issues.toolport.example/acme/sdk/issues/412"
  }
}

Limits and edge cases

issue_number is a numeric input, not a URL, title or string prefixed with #. Pair it with the correct repository; #412 in another repository is a different issue.

The response contains number, title, description, state, labels, milestone and url. The .example URL above is illustrative and is not a working tracker link. Comments, attachments and revision history are not included.

NOT_FOUND means the issue was not found after repository access was established. Check the repository and number before retrying. Do not use this error to infer whether an unauthorized private issue exists.

Errors and recovery

AUTH_REQUIRED means the credential is missing or no longer valid. ACCESS_DENIED means it cannot read the repository. INVALID_ARGUMENT means an input violates this schema. RATE_LIMITED and UPSTREAM_UNAVAILABLE need an upstream recovery step, not a broader permission grant.

Full error reference

Authentication and scope