Skip to main content
Glama
YawLabs

@yawlabs/aws-mcp

Official
by YawLabs

aws_logs_tail

Read-only

Retrieve recent CloudWatch Logs events from a log group as JSON, using the same time parsing as the AWS CLI. Supports filter patterns and time windows.

Instructions

Tail CloudWatch Logs for a log group. Wraps 'aws logs tail' (not the raw FilterLogEvents API) so you get the same server-side time parsing and event-grouping the CLI uses. Returns recent events as JSON. Does NOT stream -- run once to fetch the window, then call again with a later since. For long windows (> a few hundred events), narrow via filterPattern or lower since.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
logGroupNameYesLog group name, e.g. '/aws/lambda/my-fn' or '/aws/ecs/my-service'. No leading 'logs/'.
sinceNoWindow to tail: '<number><s|m|h|d|w>'. Default '10m'. Example: '30m', '1h', '3d'.
filterPatternNoCloudWatch Logs filter pattern. E.g. 'ERROR', '"stack trace"', '[timestamp, request_id, level = ERROR, ...]'.
logStreamNamesNoRestrict to specific stream names. Overrides the default (all streams in the group).
logStreamNamePrefixNoRestrict to streams with this prefix. Mutually exclusive with logStreamNames.
profileNoOverride session profile for this call.
regionNoOverride session region for this call.
timeoutMsNoTimeout in milliseconds. Default 60000 (60s). Raise for large windows.
Behavior5/5

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

Discloses key behaviors beyond annotations: wraps 'aws logs tail' (not raw API), returns JSON, does NOT stream. No contradiction with annotations.

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?

Four sentences, front-loaded with purpose, no extraneous information. Every sentence adds value.

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?

No output schema, but description confirms returns JSON. Covers usage pattern and constraints. For a simple fetch tool, sufficiently complete.

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%, so description adds minimal extra parameter meaning. Mentions time parsing and event-grouping, but does not elaborate on individual parameters beyond 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?

Clearly states it tails CloudWatch Logs for a log group, wrapping the AWS CLI command. Distinguishes from sibling tools which are general AWS operations, not logs-specific.

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?

Provides explicit guidance on usage: run once, call again with later 'since', narrow via filterPattern or lower 'since' for long windows. Lacks explicit alternatives but no other log tool exists.

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/YawLabs/aws-mcp'

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