QuestionPunk

Notion Survey Link Database

notion_survey_link_database

Destructive

Send a survey's completed responses to an existing Notion database (dataSourceId from notion_list_databases). Questions are matched to columns by name and type, and columns the database lacks are added. With backfill (the default) the responses collected so far are sent too, on the server. Replaces any database the survey synced to before. Sends respondents' answers to Notion. Returns the survey's sync as notion_survey_sync_get does; give the user its databaseUrl.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "surveyId": "<surveyId>",
      "connectionId": "<connectionId>",
      "dataSourceId": "<dataSourceId>"
    },
    "name": "notion_survey_link_database"
  }
}

Input Schema

Name	Required	Description
`backfill`	No	Also send the responses collected before now, on the server (default true)
`surveyId`	Yes	The survey ID (from survey_list)
`connectionId`	Yes	A connected workspace's id (connections[].id from notion_status)
`dataSourceId`	Yes	The database's dataSourceId from notion_list_databases
`includeSummary`	No	Put the AI summary of each response in its page (default true)
`includeTranscript`	No	Put interview transcripts in each page (default true)

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: it replaces any database the survey previously synced to (consistent with destructiveHint=true), creates missing columns, backfills past responses on the server by default, and sends respondent answers to a third party (consistent with openWorldHint=true). It also tells the agent to surface databaseUrl from the returned sync object.

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?

It is dense and front-loaded, leading with the core action and the dataSourceId requirement. A few sentences overlap, notably 'Sends respondents' answers to Notion' after already saying responses are sent, but the rest earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, open-world write tool, the description covers the key risks and side effects: replacement of prior sync destination, automatic column creation, default backfill, and third-party data transmission. Since an output schema exists, it appropriately only notes that the return mirrors notion_survey_sync_get and highlights databaseUrl for the user.

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 coverage is 100% and each parameter already documents its source and default, so the schema does most of the work. The description adds the useful matching rule that questions map to columns by name and type, but otherwise repeats schema-level information like the backfill default.

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 and resource: sending a survey's completed responses to an existing Notion database. It explicitly contrasts with the sibling that creates a database (notion_survey_create_database) by requiring an existing dataSourceId, and names the source tool notion_list_databases.

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?

It makes clear this is for an existing database and points to notion_list_databases for the dataSourceId, which implies the create-database path is a different tool. It doesn't explicitly say when to use notion_survey_sync_start versus this tool, so the alternative routing is only implied.

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

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