Skip to main content
Glama
bruhsb
by bruhsb

paperclip_apply_company_import

Destructive

Apply a validated company import bundle to a target company. Writes new records for agents, projects, issues, and skills with configurable collision handling.

Instructions

⚠ Board-only: Apply company import

Args:

  • companyId: string — Target company UUID

  • source: union — { type: 'inline', rootPath: string, files: Record<string,string> } or { type: 'github', url: string }

  • include: object — Which resource types to apply (company, agents, projects, issues, skills)

  • target: object — { mode: 'existing_company'|'new_company', companyId: string } — must match top-level companyId

  • agents: 'all' | string[] (optional) — Agents to import (default: 'all')

  • collisionStrategy: 'rename'|'skip'|'replace' (optional) — Collision handling (default: rename)

  • selectedFiles: string[] (optional) — Subset of bundle files to apply

  • adapterOverrides: Record<string,unknown> (optional) — Adapter overrides from the preview

Returns: Import result counts (JSON only): { insertedAgents, insertedProjects, insertedIssues, insertedSkills, warnings }. Destructive — writes new records.

Examples:

  • Use when: applying a validated import bundle; run paperclip_preview_company_import first to inspect changes

  • Don't use when: you just want to inspect what would change — use paperclip_preview_company_import

Error Handling:

  • 400: invalid bundle → verify source files are well-formed

  • 401: authentication failed → check PAPERCLIP_API_KEY

  • 403: board key required → this endpoint requires board-level authentication

  • 404: company not found → verify ID with paperclip_list_companies

  • 409: conflict not resolvable with current strategy → try a different collisionStrategy

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyIdYesTarget company UUID to apply the import into
sourceYesBundle source: 'inline' provides files in the request; 'github' fetches from a repo URL
includeYesWhich resource types to apply (company, agents, projects, issues, skills)
targetYesImport destination
agentsYesWhich agents to import: literal 'all' or an array of agent URL keysall
collisionStrategyYesHow to handle name/key collisions: 'rename' (append suffix), 'skip' (leave existing), 'replace' (overwrite)rename
selectedFilesNoSubset of file paths from the bundle to apply (omit for all files in the bundle)
adapterOverridesNoAdapter-specific overrides map from the preview step (key: adapter name, value: override config)
Behavior5/5

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

Annotations provide destructiveHint=true; description adds that it writes new records, requires board-level authentication, and returns specific JSON counts. No contradictions, and sufficient behavioral context beyond annotations.

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?

Well-structured with clear sections (Args, Returns, Examples, Error Handling). Front-loaded warning. Every sentence is informative without being verbose.

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?

Covers all essential aspects given no output schema: describes return format, prerequisites (preview first), authentication, error codes, and parameter behavior. Complete enough for correct agent invocation.

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 coverage is 100%, so baseline 3. Description adds meaningful context: explains source types, include options, target validation, and collision strategy. Adds value without redundancy.

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 clearly states 'Apply company import' and explains it applies a validated import bundle, writing new records. It distinguishes from sibling paperclip_preview_company_import by noting it should be run first.

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?

Provides explicit when-to-use ('applying a validated import bundle'), when-not-to-use (inspect changes, use preview instead), and alternatives. Error handling section gives guidance on common failure scenarios.

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/bruhsb/paperclip-mcp'

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