devops-mcp

Get repository activity

get_repo_activity

Read-onlyIdempotent

Retrieve recent commits, updated issues, and pull requests for a GitHub repository since a timestamp; defaults to the last 24 hours to summarize repository activity.

Instructions

Recent commits, updated issues, and updated pull requests since a timestamp. Defaults to the last 24 hours. Returns the first page of each list only.

Input Schema

Name	Required	Description
`repo`	Yes	Repository name, without the owner
`limit`	No	Maximum number of items to return. Defaults to 10. The tool returns the first page only.
`owner`	Yes	GitHub user or organization login
`since`	No	ISO-8601 start of the window. Defaults to 24 hours before the server clock.

Output Schema

Name	Required	Description	Default
`repo`	Yes
`owner`	Yes
`since`	Yes
`until`	Yes
`commits`	Yes
`issuesUpdated`	Yes
`pullRequestsUpdated`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

It provides key behavioral constraints not present in annotations or basic schemas, specifically that it defaults to 24 hours and returns only the first page of results. This is crucial operational information for the agent.

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 brief, direct, and efficient, immediately stating what the tool does and ending with two essential constraints regarding defaults and output scope.

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 that the parameter schema is complete and the tool is read-only/idempotent, the description provides all necessary behavioral context and operational limits (defaults/paging) required for correct and safe invocation.

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

Parameters4/5

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

While the schema has 100% coverage, the description clarifies that the 'since' parameter relates to a temporal window starting point and explicitly states the pagination constraint (returns first page only), adding semantic value beyond the structured data.

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 identifies the exact resources returned: commits, issues, and pull requests. It clearly distinguishes this aggregate functionality from specific list tools like list_issues or list_open_pull_requests.

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 description sets clear expectations by mentioning the default time window (last 24 hours) and limits the scope to the first page of results, helping the agent understand its operational context and limitations.

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

Deploy Server