Carta Download Tearsheet

作者 carta6ab81016389c无许可证14 个星标收录于 2026年10月8日更新于 2026年10月8日仓库今天更新

Download tear sheets for your portfolio companies and funds on Carta. For tear sheet requests, use carta-lp-reporting-routing instead.

仅含说明Documents & Office
AI 生成的概览

通过 Carta MCP 服务器下载投资组合公司和基金的 Carta 撕页(tear sheet)。

功能
该技能引导代理在 Carta 上选择撕页模板和投资组合公司,然后启动异步生成任务。它支持针对所有基金下全部投资组合公司的快速路径,以及按基金分组的特定子集的批量路径。它会轮询任务状态,并给出生成的 PDF 撕页的临时下载链接。
适用场景
当用户想要在 Carta 上为投资组合公司或基金创建、生成、预览或下载撕页(包括批量 ZIP 包)时使用。它面向拥有有效公司上下文的 Carta 用户。
运行要求
需要连接 Carta MCP 服务器并设置有效的公司上下文;使用 mcpcartacall_tool、mcpcartalist_contexts、mcpcartaset_context 和 AskUserQuestion 工具。不附带脚本,仅为说明。
<!-- carta:plugin-version -->

<carta-plugin>carta-investors:6.38.0</carta-plugin>

<!-- Part of the official Carta AI Agent Plugin -->

Download Tearsheet

Overview

Download tear sheets for your portfolio companies and funds on Carta.

The skill presents available templates and portfolio companies interactively, then routes to the appropriate workflow based on the selection:

  • All portcos across all funds → Download All: fast path — no fund breakdown needed.
  • Specific portcos (one or more) → Bulk: builds fund breakdowns, async ZIP archive, polled until complete, download URL provided.

When to Use

  • "Create a [Portco] tear sheet"
  • "Generate a tear sheet for [Portco]"
  • "Download tear sheet for all portfolio companies"
  • "Create a bulk tear sheet package"
  • "Preview the tear sheet for [Portco]"
  • "Generate tear sheets for all portcos in [Fund]"
  • "Download all tear sheets as a ZIP"
  • Other trigger phrases: "tear sheet for portco", "tear sheets for all portcos", "preview tear sheet", "generate tear sheet PDF", "create tear sheet", "download tear sheet package", "download all tear sheets".

Prerequisites

  • The Carta MCP server must be connected.
  • A firm context must be active. If not set, call list_contexts then set_context with the target firm_id before any other call.
  • No fund UUID or portco UUID needs to be known in advance — both are resolved interactively via fa:list:tearsheet_templates and fa:list:portfolio_companies.

Data Retrieval

MCP CommandPurpose
call_tool({"name": "fa__list__tearsheet_templates", "arguments": {}})List available PDF templates for the firm
call_tool({"name": "fa__list__portfolio_companies", "arguments": {}})List all portfolio companies with their fund groupings
call_tool({"name": "fa__mutate__download_all_tearsheets", "arguments": {...}})Start an async job for all portcos (fast path)
call_tool({"name": "fa__mutate__start_tearsheet_download", "arguments": {...}})Start an async bulk job for a specific portco subset
call_tool({"name": "fa__get__tearsheet_download_status", "arguments": {}})Poll for async job completion; returns "pending" or a download URL

Gate 0: Firm Context

Ensure a firm context is active. If this is your first MCP call in the session, or if subsequent calls fail with a firm/context error:

  1. Call list_contexts to see which firms are accessible.
  2. Call set_context with the target firm_id.

You do not need to ask the user for a firm UUID — the MCP session tracks the active firm.


Gate 1: Select Template

Call:

call_tool({"name": "fa__list__tearsheet_templates", "arguments": {}})

If the user mentioned a document name (e.g. "Investment Summary", "Fund Summary", "Tear Sheet"): match it against the template name field (case-insensitive, partial match).

  • Match found: Confirm with the user:

    "Found template 'Investment Summary' — is this the one you want?"

    If yes, store it and continue. If no, show the full table.

  • No match found: Tell the user, then show the full table:

    "No template named 'Investment Summary' was found for this firm. Here are the available templates — which one would you like to use?"

If no document name was mentioned:

  • One template: Confirm with user before proceeding.

  • Multiple templates: Show table, ask user to select by number:

    | # | id | Name | Orientation | Grain Level | Description ||---|----|------|-------------|-------------|-------------|| 1 | aaa-... | Q4 2024 Standard | landscape | fund | — || 2 | bbb-... | Annual Summary   | portrait  | company | Annual LP report |

Store as TEMPLATE_UUID (the template id) and TEMPLATE_NAME.


Gate 2: Select Portfolio Companies

Call:

call_tool({"name": "fa__list__portfolio_companies", "arguments": {}})

The command returns an array of portfolio companies. Each item includes name, entity_link_id, and fund_uuid.

Group them by fund_uuid and display a numbered table:

## Acme Fund I| # | Company Name | entity_link_id | fund_uuid ||---|--------------|----------------|-----------|| 1 | Portco Alpha | el-uuid-1      | fund-uuid-1 || 2 | Portco Beta  | el-uuid-2      | fund-uuid-1 |
## Acme Fund II| # | Company Name | entity_link_id | fund_uuid ||---|--------------|----------------|-----------|| 3 | Portco Gamma | el-uuid-3      | fund-uuid-2 |

Ask the user to choose:

  1. All portcos across all funds
  2. All portcos in a specific fund
  3. Specific companies — by row number or entity_link_id

Gate 3: Route

After the user selects portcos:

  • All portcos across all funds selected → proceed to Download All Flow.
  • One or more specific portcos selected → build FUND_BREAKDOWNS and proceed to Bulk Flow.

Download All Flow (all portcos)

Present a confirmation summary before starting — never proceed without explicit user approval:

Ready to generate tearsheets for all portfolio companies:
  Template:  <TEMPLATE_NAME> (<TEMPLATE_UUID>)  Scope:     All portcos across all funds
Proceed? (yes/no)

Start the bulk job using the download-all command:

call_tool({"name": "fa__mutate__download_all_tearsheets", "arguments": {  "template_uuid": "<TEMPLATE_UUID>"}})

Tell the user the job has started and polling will begin.

Poll for completion — call call_tool({"name": "fa__get__tearsheet_download_status", "arguments": {}}) every 30 seconds, up to 10 attempts (5 minutes total):

  • Response is "pending" → print progress ("Still processing... (attempt N/10)") and wait.
  • Response contains a URL → job complete. Capture as DOWNLOAD_URL.
  • Response is an error message → surface it and stop.

On timeout (10 attempts exhausted): Tell the user the job may still be running and they can check manually by asking: "Check tearsheet download status".

On success: Present the download link:

  • DO NOT try to download the artifact directly. ALWAYS present the download link.
Your tear sheets are ready!
[Download Your Tear Sheets](<DOWNLOAD_URL>)
> Note: this link is temporary and will expire — download it soon.

Bulk Flow (multiple portcos)

Build FUND_BREAKDOWNS — group entity_link_ids by fund_uuid:

json
[  {"fund_uuid": "fund-uuid-1", "entity_link_ids": ["el-uuid-1", "el-uuid-2"]},  {"fund_uuid": "fund-uuid-2", "entity_link_ids": ["el-uuid-3"]}]

Present a confirmation summary before starting — never proceed without explicit user approval:

Ready to generate bulk tearsheets:
  Template:  Q4 2024 Standard (aaa-...)  Portcos:   3 companies across 2 funds
    Acme Fund I      - Portco Alpha      - Portco Beta    Acme Fund II      - Portco Gamma
Proceed? (yes/no)

Start the bulk job:

call_tool({"name": "fa__mutate__start_tearsheet_download", "arguments": {  "template_uuid": "<TEMPLATE_UUID>",  "fund_breakdowns": <FUND_BREAKDOWNS>}})

Tell the user the job has started and polling will begin.

Poll for completion — call call_tool({"name": "fa__get__tearsheet_download_status", "arguments": {}}) every 15 seconds, up to 20 attempts (5 minutes total):

  • Response is "pending" → print progress ("Still processing... (attempt N/20)") and wait.
  • Response contains a URL → job complete. Capture as DOWNLOAD_URL.
  • Response is an error message → surface it and stop.

On timeout (20 attempts exhausted): Tell the user the job may still be running and they can check manually by asking: "Check tearsheet download status".

On success: Present the download link:

  • DO NOT try to download the artifact directly. ALWAYS present the download link.
Your tear sheets are ready!
[Download Your Tear Sheets](<DOWNLOAD_URL>)
> Note: this link is temporary and will expire — download it soon.

Error Handling

  • Firm context error: Call list_contexts and set_context to re-establish context.
  • No templates returned: The firm may not have tearsheet templates configured. Check the Carta app or contact support.
  • No portcos returned: The firm may not have portfolio companies. Verify the correct firm context is active.
  • Bulk job failure: Template or portco selection may be invalid. Retry with different selections.
  • Never retry automatically — surface the full error and let the user decide.

来源与署名

来源:carta/plugins位于plugins/carta-investors/skills/carta-download-tearsheet提交6ab8101

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架

更多来自 carta/plugins 的技能

Carta Fund Admin Requests

carta

Send work to your Carta Fund Admin team and track it. Opens a request the team reads, acts on, and replies to — the off-ramp for anything no other Carta skill or command can do. TRIGGER: "ask Carta to", "have Carta do", "send this to my fund admin", "ask my fund admin team", "can Carta do this for me", "check on my request", "did Carta reply", "what requests do I have open", "reply to Carta", "follow up on my request", plus ANY action request (create/change/send/restate/reconcile/split/fix) that no other skill or Carta command covers. NOT FOR: reporting a bug or feature request about this plugin (call fa:create:feedback directly); questions answerable from Carta data (use carta-explore-data); capital call reminders to LPs (that is a Carta command, not a Fund Admin request).

待分类14今天更新

Carta Explore Data

carta

通过查询 Carta 数据仓库并格式化结果,回答 Carta Web / Fund Admin 投资者数据问题。

Data & Analytics14今天更新

Update Note

carta

Searches for notes in the Carta CRM and helps the user update deal comments. Use this skill when the user says things like "update a note", "edit note", "update note content", "change a note", or "/update-note". Note: standalone note editing is not available via MCP — notes/comments are attached to deals and updated via the update-deal skill.

待分类14今天更新

Update Investor

carta

按 ID 或名称部分更新 Carta CRM 中已有的投资人记录。

Business & Finance14今天更新

Update Fundraising

carta

Updates an existing fundraising record in the Carta CRM. Use this skill when the user says things like "update a fundraising", "edit fundraising", "update fundraising details", "change fundraising stage", "update fundraising fields", or "/update-fundraising". Accepts a fundraising ID or name (will search if no ID provided). Only the fields explicitly provided are changed — all other fields are left untouched.

待分类14今天更新

Update Deal

carta

在 Carta CRM 中部分更新现有交易记录,仅修改用户指定的字段。

Business & Finance14今天更新