Skip to main content
Glama
gotohuman

gotoHuman MCP

Official

request-human-review-with-form

Submit structured data for human review using customizable forms to integrate approval workflows into AI agents and automations.

Instructions

Request a human review with a form. NOTE: If you don't have a form ID yet, list all available forms using the list-forms tool first. To know what to pass for fieldData, you need to fetch the schema for the form fields using the get-form-schema tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formIdYesThe form ID to request a human review for
fieldDataYesThe field data to include in the review request. Note that this is a dynamic schema that you need to fetch first using the get-form-schema tool.
metadataNoOptional additional data that will be incl. in the webhook response after form submission. Incl. everything required to proceed with your workflow.
assignToUsersNoOptional list of user emails to assign the review to

Implementation Reference

  • The asynchronous handler function that implements the core logic of the tool: initializes GotoHuman, creates a review request, dynamically adds field data and optional metadata/users, sends the request, and returns the review ID and link or an error.
    async ({ formId, fieldData, metadata, assignToUsers }) => {
      try {
        const gotoHuman = new GotoHuman();
        const reviewRequest = gotoHuman.createReview(formId);
    
        // Add all field data dynamically
        Object.entries(fieldData).forEach(([key, value]) => {
          reviewRequest.addFieldData(key, value);
        });
    
        // Add optional metadata if provided
        if (metadata) {
          Object.entries(metadata).forEach(([key, value]) => {
            reviewRequest.addMetaData(key, value);
          });
        }
    
        // Assign to specific users if provided
        if (assignToUsers) {
          reviewRequest.assignToUsers(assignToUsers);
        }
    
        const response = await reviewRequest.sendRequest();
    
        return {
          content: [{
            type: "text",
            text: JSON.stringify({
              success: true,
              reviewId: response.reviewId,
              reviewLink: response.gthLink
            })
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: JSON.stringify({
              success: false,
              error: error instanceof Error ? error.message : "Unknown error occurred"
            })
          }],
          isError: true
        };
      }
    }
  • Zod schema defining the input parameters for the tool: formId (required string), fieldData (object), optional metadata and assignToUsers.
    const requestHumanReviewSchema = {
      formId: z.string().describe("The form ID to request a human review for"),
      fieldData: z.record(z.string(), z.any()).describe("The field data to include in the review request. Note that this is a dynamic schema that you need to fetch first using the get-form-schema tool."),
      metadata: z.record(z.string(), z.string()).optional().describe("Optional additional data that will be incl. in the webhook response after form submission. Incl. everything required to proceed with your workflow."),
      assignToUsers: z.array(z.string()).optional().describe("Optional list of user emails to assign the review to")
    };
  • src/index.ts:100-151 (registration)
    The server.tool() call that registers the tool with its name, description, schema reference, and handler function.
    server.tool(
      "request-human-review-with-form",
      "Request a human review with a form. NOTE: If you don't have a form ID yet, list all available forms using the list-forms tool first. To know what to pass for fieldData, you need to fetch the schema for the form fields using the get-form-schema tool.",
      requestHumanReviewSchema,
      async ({ formId, fieldData, metadata, assignToUsers }) => {
        try {
          const gotoHuman = new GotoHuman();
          const reviewRequest = gotoHuman.createReview(formId);
    
          // Add all field data dynamically
          Object.entries(fieldData).forEach(([key, value]) => {
            reviewRequest.addFieldData(key, value);
          });
    
          // Add optional metadata if provided
          if (metadata) {
            Object.entries(metadata).forEach(([key, value]) => {
              reviewRequest.addMetaData(key, value);
            });
          }
    
          // Assign to specific users if provided
          if (assignToUsers) {
            reviewRequest.assignToUsers(assignToUsers);
          }
    
          const response = await reviewRequest.sendRequest();
    
          return {
            content: [{
              type: "text",
              text: JSON.stringify({
                success: true,
                reviewId: response.reviewId,
                reviewLink: response.gthLink
              })
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: "text",
              text: JSON.stringify({
                success: false,
                error: error instanceof Error ? error.message : "Unknown error occurred"
              })
            }],
            isError: true
          };
        }
      }
    );
Behavior3/5

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

With no annotations provided, the description carries the full burden. It mentions that metadata is included in webhook responses and that assignments are optional, adding some behavioral context. However, it lacks details on permissions, rate limits, or what happens after submission (e.g., review workflow), leaving gaps for a mutation tool.

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?

The description is front-loaded with the core purpose, followed by concise prerequisite notes. Every sentence serves a clear purpose—no redundancy or fluff—making it efficiently structured and easy to parse.

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

Completeness4/5

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

Given no annotations and no output schema, the description does well by covering prerequisites and parameter nuances. However, as a mutation tool, it could benefit from more details on behavioral outcomes (e.g., review process, error handling), slightly limiting completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds value by explaining that fieldData requires fetching a dynamic schema via get-form-schema and that metadata aids workflow continuity, enhancing understanding beyond the schema's technical definitions.

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?

The description clearly states the action ('Request a human review') and the resource ('with a form'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from its siblings (get-form-schema, list-forms) beyond mentioning them as prerequisites, so it lacks full sibling distinction.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool: after obtaining a form ID from list-forms and field data schema from get-form-schema. It clearly outlines prerequisites and references alternatives, ensuring proper sequencing and context.

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/gotohuman/gotohuman-mcp-server'

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