QuestionPunk

Prolific Study List

prolific_study_list

Read-onlyIdempotent

List a survey's Prolific recruitment studies, newest first, with live status from Prolific (UNPUBLISHED, ACTIVE, PAUSED, ...), submissions, places taken, and reward and costs in dollars. Pass an item's id as studyId to prolific_study_get. Needs edit access to the survey. Read-only: studies are drafted, published and managed in the QuestionPunk app.

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>"
    },
    "name": "prolific_study_list"
  }
}

Input Schema

Name	Required	Description	Default
`surveyId`	Yes	The survey ID (from survey_list)

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, open-world behavior, and the description is consistent with them while adding real context: results are ordered newest first, statuses come live from an external system, and the call requires edit access. It goes beyond the annotation set rather than restating it.

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

Conciseness5/5

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

Three tight sentences; the core action and ordering come first, then the detail-tool handoff, then the access/read-only caveat. No filler and no redundancy with the schema.

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?

Given a one-parameter, read-only list tool with full annotation coverage and an output schema, the description supplies everything missing: ordering, data freshness, permission requirement, and the path to detailed data. An agent can call it correctly without further inference.

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?

The single parameter is fully described in the schema ('The survey ID (from survey_list)'), so the baseline is 3. The description's mention of passing an item's id as studyId to prolific_study_get implies the output carries ids, but it adds no format or validation detail for surveyId itself.

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 ('List a survey's Prolific recruitment studies') plus ordering ('newest first') and returned fields (status, submissions, places taken, reward and costs). It explicitly distinguishes itself from prolific_study_get by naming the sibling and the handoff key.

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?

Clearly frames the use case (enumerate a survey's studies, inspect live Prolific status) and routes to prolific_study_get for per-study detail. The 'Needs edit access' prerequisite and 'Read-only: studies are managed in the QuestionPunk app' note set expectations about what this tool cannot do, though no other siblings (e.g., prolific_study_calc_cost, prolific_count_participants) are contrasted.

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?