Skip to main content
Glama
mguttmann
by mguttmann

Listing results

action1_list_instance_endpoint_results
Read-onlyIdempotent

Retrieve endpoints where a specific automation instance is applied or executed, enabling status tracking and audit of automation results.

Instructions

Listing results. Gets a list of endpoints where the automation instance is being applied or has been executed. 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.
verboseNoSkip per-item compactor.
instance_idYesProvide a specific instance ID.
last_statusNoSpecify the last status of the automation instance.
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, idempotentHint, and destructiveHint. The description adds the 'view_automations' permission requirement and clarifies that the tool lists endpoints where the instance is applied or executed, providing useful behavioral context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but includes a redundant first sentence ('Listing results.'). It could be more concise by merging into one sentence. The permission info is useful but not 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?

Given the comprehensive schema (100% parameter descriptions) and output schema, the description is fairly complete. It could briefly mention pagination or filtering, but the schema covers that. The permission mention adds value.

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%, so the schema already documents all 11 parameters. The description adds no additional parameter meaning, so baseline 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 action (listing results) and the specific resource (endpoints for an automation instance). It also mentions the required permission, making it distinct from sibling list tools like list_automation_instances or list_endpoints.

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 does not provide explicit guidance on when to use this tool versus alternatives, such as when to use list_automation_instances or list_automation_deployment_statuses. The purpose is implied but not contrasted with siblings.

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