Skip to main content
Glama

list_action_runs

List Gitea Actions workflow runs in a repository with pagination and filters for branch, event, status, actor, or head SHA. Get run IDs to cancel or rerun workflows.

Instructions

List Gitea Actions workflow runs in one repository. Paginated: page is 1-based, limit <= 100; keep paging until a page returns fewer than limit. Filters: branch, event (push, pull_request, schedule, etc.), status (pending, queued, waiting, in_progress, running, success, failure, skipped, cancelled), actor (username that triggered the run), head_sha. The response is a wrapper object { workflow_runs: [...], count: number } — the runs live under the workflow_runs key, NOT at the top level. Use this to find a run's id before calling get_action_run, cancel_action_run, or rerun_action_run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
repoNoRepository name (defaults to GITEA_DEFAULT_REPO)
actorNoFilter by the user who triggered the run (username)
eventNoFilter by trigger event (e.g. push, pull_request, schedule)
limitNoRuns per page
ownerNoRepository owner (defaults to GITEA_DEFAULT_OWNER)
branchNoFilter by head branch name
statusNoFilter by run status: pending, queued, waiting, in_progress, running, success, failure, skipped, cancelled
head_shaNoFilter by the head commit SHA
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It thoroughly describes pagination (1-based, limit ≤100, keep paging), response structure (wrapper object with workflow_runs key), and filter behaviors.

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 dense paragraph but well-structured: purpose, pagination, filters, response format, usage hint. Every sentence earns its place with zero redundancy.

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

Completeness5/5

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

Given 9 parameters and no output schema, the description fully covers pagination mechanics, filter options, response structure, and relationship to sibling tools. It is complete for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, yet the description adds significant meaning: it clarifies the 1-based page, provides example event values, lists all possible statuses, and explains the response structure, going well beyond the schema.

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 it lists Gitea Actions workflow runs in one repository, and explicitly mentions it is used to find a run's id before calling get_action_run, cancel_action_run, or rerun_action_run, distinguishing it 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 Guidelines4/5

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

The tool description provides clear context on when to use it (to list runs, find run id) and names alternative tools like get_action_run. It lacks explicit 'do not use' guidance but otherwise is strong.

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/amonstack/gitea_mcp'

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