Call site.request
Do something through a site's own backend — 'save that through the site's admin', 'add a record the way the site does it', 'hit my site's own API for me'. Call one of this site's OWN routes — its admin save route, its API — signed in as the member, exactly as their browser would. Use it to operate a site's own backend: add a record, change a setting, read an admin listing. The path is site-local and starts with a slash; the site decides what each route does, so read the site's code or ask the member rather than guessing a route or a body shape. A members-only route is reachable this way and no other way from chat. A GET runs straight away; a POST, PUT, PATCH or DELETE changes the live site, so the member sees the method, the path and the site on a card and approves it before anything is sent. Not for reading or changing the site's own database — that is site.database.query or site.database.execute. Over the API it answers in two calls: without confirmation_id it proposes — says what would happen, returns a confirmation_id and changes, spends and sends nothing; the same arguments again with that confirmation_id, on a member's own API key, do it.
Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.
Request
- Base URL: https://app.goosybear.ai
- URL: https://app.goosybear.ai/api/v1/tools/site.request
- Auth: HTTP bearer
Headers
Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.
Request body
Response
The call was admitted and dispatched. ok says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.
Changes
No recorded changes to this operation across all 5 revisions of this API.