Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search Tracker worklog

tracker_worklog_search
Read-onlyIdempotent

Search worklog entries across every issue by author, creation-time range, or both. Find time logs org-wide instead of reviewing one issue at a time.

Instructions

Org-wide worklog entries filtered by author and/or a creation-time range.

Unlike worklog_list (one issue), this searches every issue's worklog. body.createdBy scopes to a user and body.createdAt to a time window; both are optional. E.g. {"body": {"createdBy": "ann", "createdAt": {"from": "2026-01-01T00:00:00"}}}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesTyped request body for ``POST /worklog/_search``: by author, by creation time, or both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.122.1
    • addedInput schema / properties / body
      Added value: +{
+  "additionalProperties": false,
+  "description": "Typed request body for ``POST /worklog/_search``: by author, by creation time, or both.",
+  "properties": {
+    "createdAt": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "description": "A range of creation times (``createdAt`` of a worklog search).",
+          "properties": {
+            "from": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ],
+              "default": null,
+              "description": "Start of the range, ``YYYY-MM-DDThh:mm:ss``."
+            },
+            "to": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ],
+              "default": null,
+              "description": "End of the range, ``YYYY-MM-DDThh:mm:ss``."
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "When the records were created."
+    },
+    "createdBy": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Login or id of the author of the records."
+    }
+  },
+  "type": "object"
+}
    • removedInput schema / properties / created_by
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Login or id of the record author to filter by."
-}
    • removedInput schema / properties / created_from
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Start of the creation-time range (``YYYY-MM-DDThh:mm:ss``)."
-}
    • removedInput schema / properties / created_to
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "End of the creation-time range (``YYYY-MM-DDThh:mm:ss``)."
-}
    • addedInput schema / required
      Added value: +[
+  "body"
+]
  2. First observedv0.67.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and idempotentHint=true, so safety and idempotency are covered. The description adds that the search spans every issue and is filter-driven, but says nothing about pagination, result caps, or required permissions on org-wide data. Adequate but not rich beyond the annotations.

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?

Three tight sentences: purpose and scope first, sibling differentiation second, parameter semantics plus a worked example last. No filler, and the most important constraint (org-wide vs single issue) is front-loaded.

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 read-only filter search with no output schema, the description covers what is filtered and how, plus the scope distinction. It leaves return shape and pagination unstated, but the rubric excuses return-value documentation when no output schema exists, so only minor gaps remain.

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 description coverage is 100%, so the baseline is 3; the description earns a notch more by naming the nested fields (``body.createdBy``, ``body.createdAt``), confirming both are optional, and giving a concrete request-body example that shows how they combine.

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 (search worklog entries) plus the scope (org-wide, every issue), and explicitly contrasts with the sibling ``worklog_list`` which covers a single issue. An agent can identify the tool's purpose without opening the schema.

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?

Explicitly contrasts with ``worklog_list`` (one issue) and states the filters are optional, giving clear selection context. It does not, however, distinguish itself from the similarly-named sibling ``tracker_worklog_list_global``, which could cause ambiguity between the two global search/list tools.

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