Skip to main content
Glama

update_study

Modify an existing user interview study by adjusting participant slots, updating visual media, or revising the interview guide to refine research parameters.

Instructions

Updates an existing study. Use this to increase interview slots, add/update media, or modify the interview guide.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
study_idYes
target_interviewsNoTotal number of interview slots for this study.
is_link_disabledNo
study_mediaNoVisual stimulus shown during all interview questions (web participants only)

Implementation Reference

  • The handler function for 'update_study' which updates the study via a PATCH request to the API.
    async (input) => {
      const { study_id, ...body } = input;
      const payload = await callUsercallApi(
        `/api/v1/agent/studies/${study_id}`,
        {
          method: "PATCH",
          body: JSON.stringify(body),
        },
      );
      return result(payload);
    },
  • Input schema definition for the 'update_study' tool.
    {
      study_id: z.string().uuid(),
      target_interviews: z
        .number()
        .int()
        .positive()
        .optional()
        .describe("Total number of interview slots for this study."),
      is_link_disabled: z.boolean().optional(),
      study_media: z
        .object({
          type: z
            .enum(["image", "prototype"])
            .describe(
              "Media type: 'image' for direct image URLs (.png, .jpg, .gif, .webp) or 'prototype' for Figma prototype URLs",
            ),
          url: z.string().url().describe("Public URL to the image or Figma prototype"),
          description: z
            .string()
            .max(500)
            .optional()
            .describe("Alt text / context shown to participants"),
        })
        .optional()
        .describe(
          "Visual stimulus shown during all interview questions (web participants only)",
        ),
    },
  • src/index.ts:118-120 (registration)
    Tool registration for 'update_study'.
    server.tool(
      "update_study",
      "Updates an existing study. Use this to increase interview slots, add/update media, or modify the interview guide.",
Behavior2/5

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

No annotations provided, so description carries full burden. States it's an update operation but lacks critical behavioral details: partial vs full replacement, validation rules, error handling for non-existent studies, or side effects.

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?

Two sentences, zero waste. Front-loaded with main action ('Updates'), followed by specific use cases. Every word earns its place.

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

Completeness3/5

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

With no annotations, no output schema, and 50% param coverage, gaps remain. Description covers primary use cases but doesn't compensate for missing behavioral details or undocumented parameters. Adequate but incomplete.

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 50% (target_interviews and study_media have descriptions; study_id and is_link_disabled do not). Description maps use cases to the two documented parameters but fails to explain the undocumented boolean 'is_link_disabled' or required 'study_id'. Baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb ('Updates') and resource ('existing study'). Lists specific use cases (interview slots, media). Distinguishes from siblings implicitly (update vs create/delete/get), though 'modify interview guide' doesn't map clearly to any schema parameter.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides specific usage scenarios ('Use this to increase interview slots...'), but lacks explicit differentiation from siblings (e.g., when to use create_study vs this) and no guidance on when not to use the tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/junetic/mcp-usercall'

If you have feedback or need assistance with the MCP directory API, please join our Discord server