Skip to main content
Glama
Sign In
AWS MCP Server

AWS MCP Server

by marcelobrake
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

aws_codebuild_list_builds_for_project

Retrieve recent build IDs for an AWS CodeBuild project to monitor and analyze build history, supporting sorting by date for efficient tracking.

Instructions

List recent build IDs for a CodeBuild project.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_name": "<project_name>"
    },
    "name": "aws_codebuild_list_builds_for_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoAWS profile name from ~/.aws/config (e.g., 'default', 'production')
regionNoAWS region override (e.g., 'us-east-1', 'sa-east-1')
project_nameYesCodeBuild project name
sort_orderNoSort order (default: DESCENDING — most recent first)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral burden. It mentions 'recent' but fails to define what constitutes recent (last N builds? time window?) or disclose pagination behavior, rate limits, or that this is a read-only operation.

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

Conciseness4/5

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

Single sentence of 7 words with zero redundancy. Front-loaded with the action but slightly too terse given the lack of annotations and output schema—could accommodate one more clause about pagination or output format without losing clarity.

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?

Adequate for a listing operation with complete input schema, but gaps remain: it doesn't clarify what 'recent' means (AWS API typically returns 100 most recent), doesn't mention the output format (array of ARNs or IDs?), and omits pagination despite this being a common AWS pattern.

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?

With 100% schema description coverage across 4 parameters, the schema adequately documents each field. The description implies project_name via 'for a CodeBuild project' and hints at sort_order via 'recent', but adds no syntax or constraint details beyond the schema baseline.

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 specifies the verb (List), resource (build IDs), and scope (for a CodeBuild project), clearly distinguishing from siblings like aws_codebuild_batch_get_builds (which gets full build details) and aws_codebuild_list_projects (which lists projects). However, it doesn't explicitly name siblings for comparison.

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 provided on when to use this versus batch_get_builds or list_projects. No mention of prerequisites like needing the project to exist first, or typical use cases (e.g., monitoring recent builds).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools