Skip to main content
Glama

kaiten_get_company_activity

Retrieve company-wide activity with filters by action, author, or time range. Use cursor-based pagination to handle large datasets.

Instructions

Get company-wide activity feed. Supports cursor-based pagination for large datasets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 50, max 100)
fieldsNoComma-separated field names to keep. Strips everything else.
offsetNoPagination offset
actionsNoComma-separated action types to filter (card_add, card_move, card_archive, card_join_board, card_revive, card_delete, comment_add, checklist_add, member_add, etc.)
compactNoStrip heavy fields (avatars, user details). Default true for bulk.
author_idNoFilter by author user ID
cursor_idNoCursor-based pagination: ID of last item (use with cursor_created)
created_afterNoFilter activities after this datetime (ISO 8601)
created_beforeNoFilter activities before this datetime (ISO 8601)
cursor_createdNoCursor-based pagination: datetime of last item (more efficient than offset for large datasets)
Install Server

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It usefully mentions cursor-based pagination and the feed's company-wide scope, but it does not disclose auth requirements, rate limits, or return format. The read-only nature is implied by 'Get' but not explicitly confirmed.

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?

Exactly two sentences with no filler. Scope is front-loaded ('Get company-wide activity feed') and the mention of cursor pagination earns its place by signailing an important behavior for large datasets.

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

Completeness3/5

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

All 10 parameters are optional and well-documented, so an agent can construct valid calls from the schema alone. However, with no output schema and no annotations, the minimal description leaves the agent without explicit information about response structure, permission expectations, or the practical difference from 'all space activity' tooling.

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% and every parameter has a meaningful description, including cursor guidance ('use with cursor_created') and defaults. The description adds no parameter-level semantics beyond the schema, so baseline 3 is appropriate.

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 a specic verb ('Get') and resouce ('company-wide activity feed'), and 'company-wide' provides scope that distinguishes it from the space/card activity siblings. However, it does not explicitly differentiate it from similar siblings like kaiten_get_all_space_activity, leaving mild ambiguity.

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?

The description implies it should be used for company-wide activity, but it does not state when to prefer this tool over alternatives like kaiten_get_space_activity, kaiten_get_card_activity, or kaiten_list_audit_logs. No exclusions or 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.

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/ViktorOgnev/kaiten-mcp'

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