CrunchJunkie

update_project_settings

Change a client's AI-visibility project settings beyond scanning: brand name, product type, the Brand Profile, pause or resume the project, Local-GEO fields (locality, region, Google Business Profile URL, service areas), the brand's own off-site channel URLs, the monthly perception email opt-in, target attributes, declared brand facts for fact-checking, and the Follow-up-Survival opt-in. Only the fields passed are changed; array fields replace the stored list. Changing brandName changes how mentions are matched from the next scan onward. Requires MCP write actions; without confirm:true it returns a preview.

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": "update_project_settings"
  }
}

Input Schema

Name	Required	Description
`active`	No	false pauses the whole project (no scheduled scans); true resumes. Writes a timeline note.
`region`	No	Local GEO: region/state. Null clears.
`confirm`	No	Set true to apply. Omit for a preview. With confirm:true, also pass the preview's previewToken.
`isLocal`	No	Local-GEO mode on/off.
`profile`	No	Brand Profile free-text fields — MERGED onto the existing profile; only the keys passed change.
`clientId`	No	Client id — alternative to projectId.
`locality`	No	Local GEO: town/city. Null clears.
`brandName`	No	The brand name mentions are matched against. Changing it affects matching from the NEXT scan; history keeps the old matching.
`projectId`	No	AI-visibility project id.
`brandFacts`	No	Declared factual claims to fact-check against what AI says, one line each (max 15, 200 chars) — REPLACES the stored list.
`productType`	No	What the brand sells, e.g. "marketing agency". Null clears it.
`previewToken`	No	With confirm:true: the previewToken from this tool's preview (valid 15 minutes, once, for exactly the previewed arguments).
`serviceAreas`	No	Local GEO: service areas — REPLACES the stored list (max 25).
`offSiteChannels`	No	The brand's OWN off-site profile URLs (YouTube/LinkedIn/Reddit/…) for off-site citation attribution — REPLACES the stored list. A handle, not a bare host.
`perceptionEmail`	No	Monthly perception email on/off for this project.
`targetAttributes`	No	Attributes the brand WANTS to be known for (scored by the Messaging-gaps widget) — REPLACES the stored list (max 20).
`followUpSurvivalEnabled`	No	Follow-up-Survival (multi-turn) opt-in for this project.
`googleBusinessProfileUrl`	No	Local GEO: the brand's Google Business Profile URL (http or https). Null clears.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 24, 2026
- changedInput schema / $schema
```
Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
```
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / profile / additionalProperties
```
Removed value: -false
```

Changed4 schema fields changedOct 22, 2026

changedInput schema / properties / googleBusinessProfileUrl / description

Previous value: -"Local GEO: the brand's Google Business Profile URL (must be http/https). Null clears."New value: +"Local GEO: the brand's Google Business Profile URL (http or https). Null clears."

changedInput schema / properties / offSiteChannels / description

Previous value: -"The brand's OWN off-site profile URLs (YouTube/LinkedIn/Reddit/…) for off-site citation attribution — REPLACES the stored list. Include the handle, not a bare host."New value: +"The brand's OWN off-site profile URLs (YouTube/LinkedIn/Reddit/…) for off-site citation attribution — REPLACES the stored list. A handle, not a bare host."

changedInput schema / properties / perceptionEmail / description

Previous value: -"Monthly \"How AI describes you\" email on/off for this project."New value: +"Monthly perception email on/off for this project."

changedInput schema / properties / profile / description

Previous value: -"Brand Profile free-text fields — MERGED onto the existing profile; only the keys you pass change."New value: +"Brand Profile free-text fields — MERGED onto the existing profile; only the keys passed change."

First observedOct 19, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations only say it is a non-destructive write; the description adds the crucial preview/confirm gate ('without confirm:true it returns a preview'), the MCP write-action requirement, array-replace vs. merge behavior, and the delayed effect of brandName on the next scan. These are exactly the traits an agent cannot infer from the structured fields.

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?

The opening sentence is a long comma-separated inventory of fields that largely duplicates the fully documented schema; the genuinely load-bearing content (partial update, array replace, brandName timing, preview/confirm) is buried at the end. Front-loading the preview gate would tighten it considerably.

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?

For an 18-parameter mutation tool with a nested profile object and no output schema, the description covers merge semantics, destructive-scope limits, auth and the two-step confirm flow. It leaves the clientId-vs-projectId choice and failure/preview-expiry behavior to the schema.

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 description coverage is 100% and already documents per-parameter semantics (null clears, REPLACES stored list, previewToken lifetime). The description restates a subset (array replacement, brandName timing) but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

Specific verb (change settings) plus a named resource (AI-visibility project) and an explicit enumeration of the settable domain, scoped by 'beyond scanning' which separates it from update_scan_settings. An agent can distinguish it from sibling settings tools without reading the schema.

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 'beyond scanning' qualifier plus 'Only the fields passed are changed' establishes both when to reach for this tool and its partial-update semantics. It does not name update_scan_settings/update_report_settings as explicit alternatives, so the routing is implied rather than stated.

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

All CrunchJunkie 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?