Skip to main content
Glama
eyalbarash
by eyalbarash

cigchat_team_ticket_lists_log_data

Fetch ticket list change logs for a list ID, with optional filters by user, flow, column, item, or time range, to audit and track modifications.

Instructions

Get the ticket list change log data [GET /team/ticket-lists/{listId}/log-data] Requires the "Manage Team" scope on the token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of items in the response, between 1 and 100
listIdYesList Id
flow_nsNoSearch for list items by flow_ns Accepts either the flow namespace id or the flow's exact name — the server resolves names automatically.
user_nsNoSearch for list items by user_ns
end_timeNounix timestamp between 6 months ago and now, e.g. 1786123679.
start_timeNounix timestamp between 6 month agos and now, e.g. 1786123679.
column_nameNoSearch for list items by column name, available values: select1, select2, select3, select4, select5
list_item_idNothe list item id
Behavior3/5

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

The description discloses the authentication requirement ('Requires the "Manage Team" scope'), which is a valuable behavioral trait. The verb 'Get' and endpoint method 'GET' imply a read-only operation. However, with no annotations provided, the description carries the burden but does not cover other behavioral aspects like pagination, response format, or data limitations.

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?

The description is a single sentence, front-loaded with the action, and includes the exact endpoint and auth requirement. Every piece of information earns its place with no redundancy or filler.

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

Completeness2/5

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

The tool has 8 parameters, no output schema, and no annotations. The description only states the endpoint and scope, omitting information about the response structure, what the log data contains, or how it should be used. Given the complexity, this is insufficient for an agent to fully understand the tool's behavior.

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%, meaning all 8 parameters are already documented in the input schema. The description adds no parameter-specific semantics beyond what the schema provides, so the baseline score of 3 is appropriate.

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 tool's function with a specific verb and resource: 'Get the ticket list change log data'. It also includes the exact endpoint path, which unambiguously identifies the operation and distinguishes it from sibling tools like team_ticket_lists and team_ticket_lists_items.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as team_ticket_lists_items or team_ticket_lists. It mentions the required scope but does not explain use cases, prerequisites, or situations where this tool should be preferred. This is a clear gap.

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/eyalbarash/cig-chat-mcp'

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