Skip to main content
Glama

subir_midia_clickup

Destructive

Upload ClickUp task attachments to the client's PostGrowth media library for client approval, replacing existing media only with explicit confirmation.

Instructions

⚠️ AÇÃO REAL E IRREVERSÍVEL — NÃO USE SEM CONFIRMAÇÃO EXPLÍCITA DE UMA PESSOA, NESTA CONVERSA. Baixa os anexos da tarefa do ClickUp e faz UPLOAD REAL na biblioteca de mídia do ROI SENSEI da subconta do cliente, através do PostGrowth. A arte enviada passa a aparecer na página pública de aprovação que o cliente vê. Com confirmar_substituicao=true, a mídia que já existe no post é APAGADA e substituída pelo conjunto novo — não existe 'acrescentar uma imagem', toda escrita substitui o conjunto inteiro. Nada disso pode ser desfeito por este shim. REGRAS DE USO: (1) rode consultar_tarefa_clickup antes e mostre o vínculo à pessoa; (2) peça confirmação explícita, citando o cliente e o post; (3) só passe confirmar_substituicao=true se a pessoa autorizar apagar a arte atual, com essas palavras; (4) NUNCA use em lote nem em laço sobre várias tarefas — uma chamada por vez, cada uma com sua confirmação.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cliente_idYesUUID do cliente dono do post. Obrigatório: o servidor confere contra o banco e recusa se divergir da tarefa. É a trava contra subir arte no cliente errado.
clickup_task_idYesID da tarefa do ClickUp cujos anexos serão enviados.
confirmar_substituicaoNoSó envie true se a pessoa autorizou APAGAR a mídia atual do post. Com false (padrão), um post que já tem mídia é recusado sem que nada seja baixado ou enviado.
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), the description discloses that the action is irreversible, permanently deletes existing media when confirmed, cannot be undone, and affects the client-visible public approval page. It also clarifies that all writes replace the entire set, not additively.

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 lengthy but every sentence carries essential risk warnings or operational rules. It is well-structured with numbered usage rules, front-loaded with a danger warning, and avoids redundancy. The length is appropriate for a destructive tool.

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?

The tool is a destructive mutation with no output schema, but the description covers prerequisites, behavior, side effects, error conditions (refusal when existing media and confirmar_substituicao=false), and prohibitions. The only omission is the return format, but that is not necessary for correct selection and invocation.

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

Parameters5/5

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

While schema coverage is 100%, the description adds critical semantic guidance: cliente_id is a safeguard validated against the task, clickup_task_id is the source of attachments, and confirmar_substituicao is explained with its default and the condition for true (authorization to delete). This is more detailed than the schema descriptions.

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?

The description specifies a concrete action: downloads ClickUp task attachments and uploads them to the ROI SENSEI media library via PostGrowth. It clearly distinguishes this from sibling read tools like consultar_tarefa_clickup, which is referenced as a prerequisite. The verb and resource are explicit.

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 usage rules: run consultar_tarefa_clickup first, obtain explicit human confirmation, only use confirmar_substituicao=true with explicit authorization, and never batch. It also mentions that posts with existing media are refused unless confirmation is given, marking when to use the parameter.

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/praticacontroller-pixel/postgrowth-mcp'

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