Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Create Tracker issue remote link

tracker_remotelinks_create

Link a Tracker issue to an object in an external app and return the created link; set backlink=true to also create the mirror link in that app.

Instructions

Link a Tracker issue to an object in an external application; returns the created link.

Get the application id (origin) from applications_list. Pass backlink=true to also create the mirror link in the external app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesTyped request body for ``POST /issues/{key}/remotelinks`` (add an external link).
backlinkNoAlso create the mirror link in the external application.
issue_keyYesIssue key, e.g. QUEUE-123.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.122.1
    • changedInput schema / properties / backlink / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / backlink / description
      Previous value: -"``\"true\"`` to also create the mirror link in the external application."New value: +"Also create the mirror link in the external application."
    • removedInput schema / properties / body / properties / relationship / default
      Removed value: -"RELATES"
    • changedInput schema / properties / body / required
      Previous value: -[
-  "key",
-  "origin"
-]New value: +[
+  "relationship",
+  "key",
+  "origin"
+]
  2. First observedv0.67.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false, so the safety profile is covered. The description adds genuinely new behavior: the call returns the created link, and backlink=true causes a second side effect in the external application (a mirror link). It does not warn about duplicate links on repeat calls despite idempotentHint=false, but it goes beyond the structured fields.

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 compact sentences/paragraphs, front-loaded with the action and its return value, followed by the two operational hints. No filler and nothing repeated from the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description correctly notes that the created link is returned. Together with the origin-lookup hint and the backlink side-effect note, an agent has everything needed to invoke this nested-body create tool correctly.

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 meaning beyond the schema by naming the external source for ``origin`` (``applications_list``) and by clarifying the effect of ``backlink=true`` beyond the schema's terse wording, which is the one place an agent could go wrong.

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?

States a specific verb and resource: links a Tracker issue to an object in an external application and returns the created link. The 'external application' framing cleanly separates it from the sibling internal-link tools (tracker_links_create) and from tracker_remotelinks_list/delete.

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?

Gives a prerequisite chain ('Get the application id (``origin``) from ``applications_list``') and conditional usage ('Pass ``backlink=true`` to also create the mirror link'). It stops short of stating when-not to use it, e.g. versus tracker_links_create for intra-tracker links, so it is clear context without exclusions.

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