Google Photos MCP by Nova (CIVAI)

set_network_identity

Choose where this user's requests to the site leave from and which browser they present, only when the user asks (e.g. 'connect through Nigeria', 'use my own user agent'). Sites may ask the user to sign in again when this changes. reset=true goes back to how they signed in.

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

Input Schema

Name	Required	Description
`reset`	No	Clear the choice: back to how the user signed in.
`route`	No	app: the app's default; direct: the server; fixed: the always-on VPN exit; vpn_country: a VPN exit in `country`.
`locale`	No	e.g. en-NG
`country`	No	ISO country code for vpn_country, e.g. NG, GB, US.
`timezone`	No	IANA time zone, e.g. Africa/Lagos.
`user_agent`	No	The browser user agent to present.
`impersonate`	No	Connection fingerprint target (e.g. chrome145); derived from the user agent when left out.
`accept_language`	No	e.g. en-NG,en;q=0.9

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose a real side effect: 'Sites may ask the user to sign in again when this changes.' It also explains that reset=true restores the sign-in state. It stops short of covering persistence/duration or auth requirements for the change.

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

Conciseness4/5

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

A single dense sentence that front-loads the action, then the permission gate, then the risk note, then the reset escape hatch. The parenthetical examples earn their space; only the run-on phrasing costs it a point.

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 8-parameter, all-optional mutation tool with no annotations and no output schema, the description covers the purpose, the permission gate, the visible side effect, and the undo path. The interplay between route and country is left entirely to the schema, but the schema handles it adequately.

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%, so the enum semantics for route and the country/locale/timezone/user_agent/impersonate meanings are already fully documented. The description only adds a loose link between 'connect through Nigeria' and the country/route combination and restates the reset behavior, so it does not meaningfully exceed the schema.

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 plus a concrete dual resource: where requests egress from and which browser/user agent they present. This is clearly the write counterpart to get_network_identity and could not be confused with the calendar/asset siblings.

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 an explicit gating condition ('only when the user asks') plus concrete trigger phrasings like 'connect through Nigeria' and 'use my own user agent', which is unusually actionable. It does not name the read-side alternative (get_network_identity) for inspecting the current identity, which is the only missing piece.

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

All Google Photos MCP by Nova (CIVAI) 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?