Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List Tracker trigger webhook logs

tracker_triggers_webhook_log_list
Read-onlyIdempotent

Fetch webhook action execution logs for a trigger to review outbound HTTP requests and responses, newest first, with optional date or issue filters.

Instructions

The execution log of a trigger's HTTP-request (Webhook) action, newest first.

Each record holds the outbound request and received response for one run. Only Webhook actions produce these; a trigger with no HTTP action returns an empty list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax records (the API's default is 10, its maximum 100).
date_toNoRange end, YYYY-MM-DDThh:mm:ss.sss±hhmm.
issue_idNoOptional issue key/id to scope the logs to one issue.
queue_idYesQueue key (case-sensitive, e.g. DEV) or numeric queue id.
date_fromNoRange start, YYYY-MM-DDThh:mm:ss.sss±hhmm.
trigger_idYesNumeric identifier of the trigger.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.122.1
    • addedInput schema / properties / date_from
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Range start, YYYY-MM-DDThh:mm:ss.sss±hhmm."
+}
    • addedInput schema / properties / date_to
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Range end, YYYY-MM-DDThh:mm:ss.sss±hhmm."
+}
  2. First observedv0.67.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so safety is covered. The description adds real value beyond them: ordering (newest first), the per-record payload (outbound request plus received response), and the empty-list behavior for non-webhook triggers. No permissions or rate-limit notes, but the bar is lower with annotations present.

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?

Three short sentences, front-loaded with what the log is, followed by record contents and the empty-result caveat. Every sentence earns its place with no filler, though the third sentence is slightly defensive.

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?

With no output schema, the description steps in to describe what each returned record holds (request and response for one run) and its ordering, which is what an agent needs. For a read-only listing tool with full param schema coverage, the remaining gap (no pagination/limit interaction note) is minor.

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% and each parameter (limit, date_from/date_to, issue_id, queue_id, trigger_id) is documented in the schema itself. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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 names the specific resource ('execution log of a trigger's HTTP-request (Webhook) action') and the operation (list, newest first), so an agent knows exactly what comes back. It stops short of naming or contrasting sibling tools like tracker_triggers_list or tracker_autoactions_logs_list, which would push it to a 5.

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?

It implies the context of use ('Only Webhook actions produce these; a trigger with no HTTP action returns an empty list'), which usefully heads off a confusing empty result. However, there is no explicit guidance on when to prefer this over other trigger/autoaction log tools, so usage remains implied rather than stated.

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