Skip to main content
Glama
mguttmann
by mguttmann

Listing automation instances

action1_list_automation_instances
Read-onlyIdempotent

List automation instances to view running and completed automations, helping monitor execution status for an organization.

Instructions

Listing automation instances. Gets a list of running and completed automations for the specified organization. Perm: view_automations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNoProvide the number of the first record to be returned.
limitNoSet the maximum number of items to be returned (the page size).
cursorNoPagination cursor.
filterNoProvide a case-insensitive substring to filter and narrow down returned results (i.e., if...
org_idNoOrg UUID.
sortbyNoDefine the sorting order by a certain field.
statusNoSpecify the status.
verboseNoSkip per-item compactor.
completedNoSpecify the completion status of the automation schedule.
endpoint_idNoThe ID of the endpoint to query.
auto_paginateNoWalk all pages.
response_formatNoOutput format. Default markdown.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
countYes
itemsYes
totalNo
has_moreNo
next_cursorNo
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds that it retrieves both running and completed automations and requires the 'view_automations' permission, which is useful context beyond annotations. It does not mention pagination or any other behavioral traits, but the annotations cover safety.

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 extremely concise with two short sentences. Every word is necessary and front-loaded, providing essential information without waste.

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?

Given the tool has 12 parameters and an output schema exists (though not shown in the prompt), the description is mostly complete. It covers the purpose, scope (running/completed), and required permission. It could mention the return format or pagination behavior, but the schema and annotations fill in some gaps.

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% with well-described parameters (12 parameters, all have descriptions). The description does not add any additional meaning to the parameters beyond what the schema provides, so it meets the baseline of 3.

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 clearly states that the tool lists automation instances (running and completed) for a specified organization. The verb 'listing' and resource 'automation instances' are specific, and it distinguishes from other list tools by referring to instances rather than schedules or recent automations, but it does not explicitly differentiate from siblings.

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?

No guidance is provided on when to use this tool versus alternatives like list_automation_schedules or list_recent_automations. The description only implies it is for listing instances of an organization, but lacks explicit context or exclusions.

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/mguttmann/action1-mcp'

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