Skip to main content
Glama

Get face detection results

get_face_detection_results
Read-onlyIdempotent

Returns a face-detection job's status and detected faces. Use with the id from detect_faces to inspect progress and choose face mappings before a selected-face swap. Read-only; faces may populate while processing.

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": {
      "id": "<id>"
    },
    "name": "get_face_detection_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id of the task. This value is returned by the [face detection API](https://docs.magichour.ai/api-reference/files/face-detection#response-id).

Output Schema

NameRequiredDescriptionDefault
idYesThe id of the task. This value is returned by the [face detection API](https://docs.magichour.ai/api-reference/files/face-detection#response-id).
errorYesWhy the face detection failed. Present only when `status` is `error`; `null` otherwise.
facesYesThe faces detected in the image or video. The list is populated as faces are detected.
statusYesThe status of the detection.
credits_chargedYesThe credits charged for the task.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / error
      Added value: +{
      +  "description": "Why the face detection failed. Present only when `status` is `error`; `null` otherwise.",
      +  "properties": {
      +    "code": {
      +      "description": "An error code to indicate why a failure happened.",
      +      "example": "no_source_face",
      +      "type": "string"
      +    },
      +    "message": {
      +      "description": "Details on the reason why a failure happened.",
      +      "example": "Please use an image with a detectable face",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "message",
      +    "code"
      +  ],
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "id",
      -  "credits_charged",
      -  "status",
      -  "faces"
      -]New value: +[
      +  "id",
      +  "credits_charged",
      +  "status",
      +  "faces",
      +  "error"
      +]
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description earns credit for adding behavior not in the annotations: results are status-bearing and non-final ("faces may populate while processing"), warning the agent that an empty list may simply be an in-progress job rather than a failure.

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 short sentences: what it returns, how to use it, and the caveat about partial results. The most important information leads, and no sentence is filler.

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?

An output schema exists, so return values need no explanation, and the description covers status semantics, the partial-result caveat, and placement in the detect-then-swap flow. Minor gap: it does not indicate whether the caller should re-poll or how completion is signaled, which would help for an asynchronous job-status tool.

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?

With a single parameter at 100% schema description coverage, the schema already explains that the id is the task id returned by the face detection API. The description's "id from detect_faces" restates that origin in workflow terms but adds no format, validation, or reuse detail beyond the schema.

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?

Names a specific verb and resource ("Returns a face-detection job's status and detected faces") and implicitly contrasts with the triggering sibling detect_faces. An agent can tell this is the read/inspection half of a two-step workflow without opening the schema.

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?

Explicitly states the precondition ("Use with the id from detect_faces") and the downstream purpose ("choose face mappings before a selected-face swap"), which places it precisely in the workflow. It does not state when not to call it or note polling cadence, so it falls just short of full alternative/exclusion guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.