ReferenceWhat you can callProjectsmutateprojects.updateContext

projects.updateContext

Rewrite a workspace’s business context.

EndpointPOST /mcp/mutate
Scopewrite
Sandbox keyallowed
Extra entitlementnone
MCP toolsselda_update_project_context
Convex functionmcpQueries:updateProjectContext

A free sandbox key may call it.

Arguments

ArgumentTypeRequiredNotes
projectIdstringrequired
whatTheyDostringoptional
industrystringoptional
valuePropositionstringoptional
productsstringoptional
targetMarketsstring[]optional
jobTitlesstring[]optional
companySizestringoptional
voiceExamplesGoodstring[]optional
voiceExamplesBadstring[]optional
forbiddenPhrasesstring[]optional
toneWordsstring[]optional
competitorsstring[]optional
knownCustomersstring[]optional

What Selda fills in

You never send these. The HTTP layer overwrites them from the API key, which is what keeps one organisation’s data out of another’s reach.

ArgumentFilled in from
orgIdyour organisation, resolved from the API key

Example request

Required arguments only. Values in angle brackets are yours to fill in; the optional ones are in the table above.

curl -X POST https://api.selda.ai/mcp/mutate \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "fn": "projects.updateContext", "args": { "projectId": "<projectId>" } }'
{
  "fn": "projects.updateContext",
  "args": {
    "projectId": "<projectId>"
  }
}

Example response

Every endpoint answers in the same envelope.

{
  "value": <the function's return value>,
  "request_id": "req_..."
}

The shape of value is not documented here. mcpQueries:updateProjectContext declares no returns validator, so there is nothing to derive it from, and a shape written out by hand here is a shape that goes stale without anything noticing. Call it once against a test key and read what comes back.

On failure the body is { "error": { "type", "code", "message", "request_id" }, "request_id" } and request_id is echoed in the X-Request-Id header.


Generated from convex/lib/mcpRegistry.ts. Nothing in this reference sends: launchRun is in no registry and never will be, so a script can prepare a campaign completely and a person still presses send in the app.