Galatic.ai

Add video to artist

add_artist_project

Attach one video from the user's library to one of their AI artists, so it shows as a project on that artist's page (visible to the owner only). Returns { artistId, project } (201). Only videos can be added; a video already attached to another artist is refused (409). artistId comes from list_artists and galleryItemId from list_gallery. Deleting the video later removes it from the artist too.

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": {
      "artistId": "<artistId>",
      "galleryItemId": "<galleryItemId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "add_artist_project"
  }
}

Input Schema

Name	Required	Description
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`artistId`	Yes	artistId from list_artists.
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`galleryItemId`	Yes	A video id from list_gallery.
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026
- addedInput schema / properties / artistId / description
```
Added value: +"artistId from list_artists."
```
- addedInput schema / properties / galleryItemId / description
```
Added value: +"A video id from list_gallery."
```
First observedOct 24, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations (which already declare this is a non-read-only, non-idempotent, non-destructive mutation), it discloses the 201 response shape { artistId, project }, owner-only visibility, the 409 refusal path for already-attached videos, and the cascade behavior when the underlying video is deleted. That is meaningful behavioral context an agent could not infer from structured fields.

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 sentences, front-loaded with purpose, then return/error behavior, then ID provenance. No filler, and each sentence contributes information the agent needs.

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 5-parameter mutation tool with no output schema, the description covers purpose, preconditions, response shape, failure mode, visibility, and downstream cascade effects. Combined with annotations and full schema coverage, nothing needed to invoke it correctly is missing.

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 description coverage is 100%, so the schema already documents every parameter. The description's ID provenance notes (artistId from list_artists, galleryItemId from list_gallery) simply repeat what the schema descriptions already say, adding no new semantics; baseline 3 applies.

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?

States a specific verb and resource: attach one video from the user's library to one of their AI artists, shown as a project on that artist's page. This is unambiguous on its own, but it never contrasts with the closest sibling (save_artist), which is the likely confusion point for creating or updating an artist.

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?

Gives clear preconditions and constraints: only videos, an item already attached to another artist is refused with 409, and IDs come from list_artists and list_gallery. It does not explicitly route the agent to alternatives such as save_artist, so it stops short of full when-to-use/when-not-to-use coverage.

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

All Galatic.ai 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.