Get started

MCP tools127

Access and context
Work
Ideas
Memory
Context links
Life
Reviews and approvals
Sessions
Tasks
Projects and documents
Canvas
Task queue
Decision docs
Skills
Files
Briefings
Design
Convert

HTTP API590

Identity, sign-in and browser sessions
Accounts, organizations and personal context
Members and invitations
Launch flags and admission
Agent clients, machine keys and MCP
Suite API credentials
Work board and items
Attention and approvals
Agent sessions and review
Ideas
Memory, sources and Recall
Context links
Projects and Editor
Home dashboard
Calendar
Personal Life
Files and jobs
Briefings
Design
Security
Settings and preferences
Data lifecycle: export and deletion
Billing and subscriptions
Credits and wallet
Usage metering and spend controls
Search
Presence, page analytics and Updates
Skills
Activity
Task queue
Canvas
Agent files
Decision docs
Other operations

briefing_script_context_get

TOOLtools/call

Read approved claims and current Short options for an episode owned by your key's human owner. No source documents, storage credentials, payment or approval authority are returned.

Scopes

read:briefing_scripts

Inputs

accountIdstringRequired
serviceTenancyIdstringRequired
idstringRequired

Returns

The authorized approved claims, exact source hashes, current options, version and spoken-word band for the Short. A call returns content[0].text with the JSON result and structuredContent.result with the same value.

Listed when

The connection is a briefing queue producer with the tool's scope. Podcast script tools are not available to OAuth agents because their permissions are not offered in OAuth consent.

Request

{
  "jsonrpc": "2.0",
  "id": "example_briefing_script_context_get",
  "method": "tools/call",
  "params": {
    "name": "briefing_script_context_get",
    "arguments": {
      "accountId": "<accountId>",
      "serviceTenancyId": "<serviceTenancyId>",
      "id": "<id>"
    }
  }
}

Endpoint

POST https://mcp.specifywork.com/api/mcp

Authorization: Bearer <OAuth access token>. Your MCP client obtains the token by signing in and receiving your approval. Configure the server URL alone, with no key or Authorization header.