Skip to main content
Glama

mr_changed_files

List files changed in a GitLab merge request with stats and reviewability flags. Sort reviewable files first to prioritize high-value code review.

Instructions

List the files changed in a merge request with stats — no diff content.

The cheap entry point for large reviews: the payload has no diff content, so it stays small even on a very large MR. Each file reports additions/deletions, new/deleted/renamed flags, and a reviewability flag (lockfiles, generated code, binary assets, and enormous single-file changes are marked reviewable=false with a skip_reason). Files are ordered reviewable-first then largest-change-first, so you can batch the highest-value files straight into mr_diff_lines(url, files_filter=[...]).

Args: url: Full GitLab merge request URL.

Returns: {mr_number, title, author, branches, commits, diff_shas, files[{file_path, additions, deletions, reviewable, skip_reason, ...}], stats{total_files, reviewable_files, skipped_files, ...}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
Behavior5/5

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

With no annotations, the description carries the full burden and meets it: it discloses the output has no diff content, explains the reviewability flag and skip reasons, and specifies file ordering (reviewable-first then largest-change-first). It also provides the return shape.

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?

Description is front-loaded with a one-sentence purpose, then a compact rationale paragraph, then structured Args/Returns. Every sentence adds informational value with no filler.

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 there is no output schema, the description compensates by itemizing the return object and file fields. It fully covers behavior, ordering, and integration with sibling tools, making the tool self-contained for an agent.

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?

The single parameter (url) receives a one-line semantic clarification ('Full GitLab merge request URL') beyond the bare schema, which is sufficient for a simple string param. It doesn't enumerate URL formats or error conditions, but it's adequate.

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?

States a specific verb+resource ('List the files changed in a merge request with stats') and immediately contrasts with 'no diff content', differentiating it from sibling diff tools. The final line references mr_diff_lines for further filtering, reinforcing its distinct role.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly frames it as 'the cheap entry point for large reviews,' defines the payload size advantage, and tells the agent to batch results into mr_diff_lines, giving a concrete when-to-use pattern and alternative.

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/SurajKGoyal/myopic'

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