Angi MCP Server and API by Cotlet

Update service locations in Angi

angi_update_service_locations

Read-onlyIdempotent

Update service locations in the user's own Angi account from ChatGPT, Claude or any AI agent. Returns how to do it in Angi step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Angi Cloud Browser. Angi's official API: Angi has no public API for pros (checked 28 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "angi_update_service_locations"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds the key behavior beyond them: the tool 'opens nothing by itself' and returns a screen/button/field walkthrough. The note that Angi has no public API for pros justifies why a browser-based path is required, which is genuinely useful context an agent could not infer.

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

Conciseness3/5

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

Front-loads the resource and the return semantics, which is good, but 'from ChatGPT, Claude or any AI agent' is filler and the trailing 'Angi's official API: Angi has no public API for pros' is awkwardly phrased as a fragment. Trimming those would sharpen an otherwise tight definition.

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?

With no output schema, the description must explain what comes back, and it does (step-by-step screens, buttons, fields), plus the follow-up path through cotlet_browser_* tools. The only omission is any hint about failure modes, e.g. what happens if the user is not signed in to Angi.

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 tool takes zero parameters, so the description carries no parameter documentation burden and the schema is trivially complete. Baseline of 4 applies; nothing is misrepresented or missing.

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?

States the resource (service locations in the user's Angi account) and, crucially, what the tool actually delivers: step-by-step instructions rather than performing the update. This resolves the mismatch between the 'update' verb in the name and the read-only behavior, though the tension is only cleared in the second sentence rather than up front.

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?

Gives a clear operating context ('in the user's own Angi account') and an explicit next step: carry out the returned steps with the cotlet_browser_* tools in the Cloud Browser. It never names an alternative Angi tool or states when not to use this one, but for a guide-style tool the workflow routing is adequate.

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

All Angi MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?