Skip to main content
Glama

backlog_export_issue_context

Export a Backlog issue with all comments, attachments, and metadata into a local markdown context bundle for LLM summarization.

Instructions

Export a Backlog issue into a local raw context bundle for LLM summarization.

Fetches issue details, all comments (paginated), attachment metadata, downloads files, and writes:

  • raw.md: full markdown context with complete metadata (type, status, resolution, priority, parent, assignee, reporter, categories, milestones, versions, dates, hours), description, attachments, comments, and extracted text

  • manifest.json: machine-readable export metadata with placement confidence per attachment

Attachment placement is exact only when issue/comment text references the attachment; otherwise inferred by uploader/time or left unmatched. The output directory is configured via ATTACHMENT_WORKSPACE in the server's environment.

INPUT:

  • issueIdOrKey (required): issue key e.g. "BLG-10474" or numeric ID

  • outputDir (optional): override export root directory

  • includeComments/includeAttachments/downloadAttachments (optional booleans, default: true)

  • extractReadableFiles (optional boolean, default: false)

  • skipChangelogOnlyComments (optional boolean, default: false) — skip comments with no text (only field changes)

  • maxAttachmentBytes (optional): skip files larger than this (default: 10485760 = 10 MB)

  • placementWindowMinutes (optional): time window for inferred comment placement (default: 10)

EXAMPLE: { issueIdOrKey: "BLG-10474" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueIdOrKeyYesBacklog issue key or numeric issue ID. Example: BLG-10474
outputDirNoRoot directory for export output. Default: ATTACHMENT_WORKSPACE config value.
includeCommentsNoInclude all issue comments. Default: true.
includeAttachmentsNoInclude issue attachment metadata. Default: true.
downloadAttachmentsNoDownload attachment files. Default: true.
extractReadableFilesNoExtract text-like attachment contents into markdown. Default: false.
maxAttachmentBytesNoSkip downloading attachments larger than this many bytes. Default: 10485760.
placementWindowMinutesNoTime window (minutes) for inferred comment attachment placement. Default: 10.
skipChangelogOnlyCommentsNoSkip comments that have no text content (only field changes). Useful for translation/export workflows. Default: false.
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses key behaviors: fetching paginated comments, downloading attachments, writing two output files, and the heuristic for attachment placement. It does not cover error handling, authentication, or performance characteristics, but provides substantial detail.

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?

The description is well-structured with a main paragraph, bulleted parameter list, and example. It front-loads the purpose. However, it is somewhat verbose, repeating default values and including extensive detail on attachment placement that could be condensed.

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 tool with 9 parameters, no output schema, and no annotations, the description covers the key aspects: inputs, outputs (two files), default behaviors, and a usage example. It omits error handling and edge cases but provides sufficient context for an AI agent to invoke it correctly.

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 baseline is 3. The description adds minor context (e.g., 'override' for outputDir, 'skip comments with no text' for skipChangelogOnlyComments) but largely restates schema defaults. No significant new meaning beyond what the schema provides.

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 verb ('Export') and resource ('Backlog issue') with the specific goal of creating a local raw context bundle for LLM summarization. It distinguishes itself from siblings like backlog_get_issue by detailing the multi-file output and aggregation of comments, attachments, and metadata.

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?

While the description implies use for LLM summarization, it does not explicitly state when to use this tool versus alternatives (e.g., backlog_get_issue for raw data, backlog_get_comments for comments only). No 'when not to use' guidance is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cuongph-dev-work/backlog_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server