Skip to main content
Glama
Syfer-web
by Syfer-web

edit_file

Modify files on a live deployed site using create, replace, or delete, and ship a new patch deploy with preview URL.

Instructions

Patch a file on a live deployed site and ship a new patch deploy. The AI decides what to change; the MCP ships the patch. Returns the new deploy_id + preview_url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opYescreate = new file (requires value/content); replace = first match (requires find + value); replace_all = every match (requires find + value); delete = remove file.
fileYesPath of the file to create/replace/delete.
findNoFor replace/replace_all: the exact substring to find inside the file's current content.
valueNoFor create/replace/replace_all: the new text.
contentNoAlias for value (kept for ergonomics on create). If both given, value wins.
messageNoOptional human-readable note stored with the patch deploy.
deploy_idYesThe BASE deploy to patch on top of. The new patch deploy will have this as its parent_deploy_id.
Behavior4/5

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

With no annotations, the description effectively discloses key behaviors: applying a patch and deploying, returning deploy_id and preview_url. However, it omits details like failure handling or permission requirements.

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?

Two concise sentences with no unnecessary words, front-loading the core functionality.

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?

Given 7 parameters and no output schema, the description mentions return values and overall purpose, but lacks details on error states or side effects of the patch deploy.

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 the schema already documents each parameter well. The description adds minimal additional meaning beyond contextualizing the operations.

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 patches a file on a live site and ships a patch deploy, distinguishing it from read-only (read_file) or full deploy (ship_site) tools.

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?

Implied usage for modifying files and deploying, but no explicit when-not-to-use or alternatives listed among siblings.

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/Syfer-web/krexel-mcp'

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