Skip to main content
Glama
260,860 tools. Last updated 2026-07-05 08:54

"How to create and read issues in YouTrack project management" matching MCP tools:

  • Full-text search the ACC Docs module on a project for drawings, specs, submittals, and other documents matching a query string. Calls the APS Data Management v1 search endpoint scoped to a project. When to use: an agent needs to locate a spec section, a sheet, or a submittal by keyword (e.g. 'fireproofing', 'A-101', 'RFI 23'). When NOT to use: you already have the document URN/lineage — fetch it directly. You want the file contents — this returns metadata; download separately via Data Management. APS scopes: data:read account:read Rate limits: APS default ~50 req/min per app per endpoint; Model Derivative translation jobs ~60 req/min; OSS uploads size-limited per file to 100MB for direct upload, larger via resumable. Errors: 401 APS token expired/invalid — refresh; 403 scope or resource permission denied (Docs module access required); 404 project_id not found — check the ID (note: this endpoint re-prepends 'b.' so pass the UUID form); 429 rate limited — backoff and retry; 5xx APS upstream outage — retry with jitter. Side effects: READ-ONLY. Inserts a row into D1 usage_log. Idempotent.
    Connector
  • Create a new project on your account so an agent can bootstrap from a fresh account. The slug is derived from the name and validated server-side (format, reserved words, uniqueness). Each plan includes a fixed number of active projects (free tiers one; paid plans more — see list_subscription_plans); at the limit this returns an error telling you to archive a project or upgrade. Requires an ACCOUNT-scoped token and the `config` scope. Returns the created project ({id, slug, name, apiBaseUrl, archived}); mint a project-scoped token in the panel to then configure it.
    Connector
  • Full-text search the ACC Docs repository of a project for drawings, specs, submittals, and other files via the APS Data Management search endpoint. When to use: The user wants to find a document by keyword (filename, sheet number, or metadata match). E.g. 'find the latest A-201 sheet' or 'search for mechanical specs on Tower project'. When NOT to use: Do not use to upload a file (use acc_upload_file); do not use to fetch issues/RFIs. If you already have a document URN, fetch it directly with an agent that has Data Management folder/item access. APS scopes: data:read account:read. No write scope required. Rate limits: APS Data Management ~50 req/min per app per endpoint; pageable (limit 200 upstream). Avoid tight query loops. Errors: 401 (APS token expired — refresh); 403 (user lacks Docs view permission on the project); 404 (project_id not found — verify 'b.' prefix and hub membership); 422 (invalid filter syntax — simplify query text); 429 (rate limit — back off 60s); 5xx (ACC upstream — retry with jitter). Side effects: None. Read-only and idempotent.
    Connector
  • Upload a file from a public source URL into an ACC project folder. Runs the full four-step APS Data Management flow: top-folder discovery → storage object creation → OSS PUT of bytes → first-version item creation. When to use: The user wants to push a document/photo/model into ACC Docs — e.g. 'upload this site photo to the Tower project Photos folder' or an automation needs to archive an exported report into Project Files. When NOT to use: Do not use for files already in ACC; do not use for files behind auth-gated URLs (fetch step is an unauthenticated GET). For very large files (>100MB), prefer the chunked/signed-S3 upload flow, not this single-PUT implementation. APS scopes: data:read data:write data:create account:read. Rate limits: APS Data Management ~50 req/min per endpoint; OSS upload bandwidth typically 100 MB/min per app. This tool issues 3–5 APS calls per upload, so budget accordingly. Errors: 401 (APS token expired — refresh); 403 (user lacks folder write permission — ask account admin to grant 'Edit' on folder); 404 (project_id not found or folder_path does not match any top folder — verify 'b.' prefix, hub membership, and folder name); 422 (invalid file_name or conflicting version); 429 (rate limit — back off 60s); 5xx (ACC/OSS upstream — retry with jitter BUT be cautious: storage object may already be created so reuse, do not re-create). Also: if source file_url returns non-2xx, the tool throws before touching ACC. Side effects: Creates a storage object, uploads bytes, and creates a versioned item in the target folder. NOT idempotent — a retry may create a duplicate item with a new version. Surface the returned item_id to the user to avoid re-uploads.
    Connector
  • Fetch the full ACC project metadata record (name, type, status, dates, extension attributes) for a single project via APS Data Management. If hub_id is omitted the tool picks the first accessible hub, which may be wrong on multi-hub tenants. When to use: The user asks 'tell me about project X' or an agent needs project metadata (start/end dates, type, Forma/BIM 360 flavor) before deciding which downstream tool to call. When NOT to use: Do not use as a cheap existence check — prefer acc_list_projects which returns hub_id with every project and is one call regardless of tenant size. APS scopes: data:read account:read. Forma / BIM 360 hubs endpoints only require data:read. Rate limits: APS default ~50 req/min per endpoint; BIM 360 hubs endpoints pageable (limit 200). Cache results for the session. Errors: 401 (APS token expired — refresh); 403 (user lacks project view or app not in account); 404 (project not in the chosen hub — supply the correct hub_id, or call acc_list_projects first); 422 (malformed project_id — confirm 'b.' prefix); 429 (rate limit — back off 60s); 5xx (ACC upstream — retry). Side effects: None. Read-only and idempotent.
    Connector
  • Read-only preview: for each given printer, return the next queue item that would be started. Uses the same dedup matcher as create_print_job with next_queue_item=true, so the same queue item is never returned twice across printers in one call. Includes match failures per printer (issues) so you can explain why a printer has nothing to print. Does NOT start any job.
    Connector

Matching MCP Servers

  • A
    license
    B
    quality
    D
    maintenance
    A Model Context Protocol (MCP) server for YouTrack integration, providing a standardized interface for LLMs to interact with YouTrack's issue tracking, agile management, and knowledge base features.
    Last updated
    12
    45
    MIT

Matching MCP Connectors

  • Create, edit, preview, publish, and manage web pages from MCP-capable AI clients.

  • Create AI surveys with dynamic follow-up probing directly from your AI assistant.

  • Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Honeydew Documentation documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path (e.g. `/quickstart.mdx`, `/api-reference/create-customer.mdx`) to `head` or `cat`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage. Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /api-reference && ls` or `ls /api-reference`). Do NOT assume that `cd` in one call affects the next call. Examples: - `tree / -L 2` — see the top-level directory layout - `rg -il "rate limit" /` — find all files mentioning "rate limit" - `rg -C 3 "apiKey" /api-reference/` — show matches with 3 lines of context around each hit - `head -80 /quickstart.mdx` — read the top 80 lines of a specific page - `head -80 /quickstart.mdx /installation.mdx /guides/first-deploy.mdx` — read multiple pages in one call - `cat /api-reference/create-customer.mdx` — read a full page when you need everything - `cat /openapi/spec.json | jq '.paths | keys'` — list OpenAPI endpoints Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible. When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/quickstart.mdx` becomes `/quickstart` and `/api-reference/overview.mdx` becomes `/api-reference/overview`.
    Connector
  • Returns the canonical guide for using TMV from a coding-agent context. Covers the fix-test-retest loop, how to write a good test prompt, how to read the actionTrail / consoleErrors / failedRequests outputs, and common gotchas. Call this first if you're a new agent on a project — it'll save you a debug session. The same content is served at https://testmyvibes.com/docs/coding-agents.
    Connector
  • Enumerate every ACC and BIM 360 project the authenticated APS app can see by walking all accessible hubs and their project lists. When to use: The agent needs to discover project IDs before calling any other tool (e.g. the user says 'show me my projects' or 'find issues in the Tower project' and no project_id is known yet). Also useful to confirm hub membership for a project. When NOT to use: Do not call this repeatedly in a loop — cache the result; if the user already supplied a project_id starting with 'b.', skip discovery. APS scopes: data:read account:read. No write scope needed. Rate limits: APS default ~50 req/min per app per endpoint; BIM 360 hubs endpoints are pageable (limit 200). This tool fans out 1 hubs call + N project calls (one per hub) so call it sparingly on tenants with many hubs. Errors: 401 (APS token expired — refresh and retry once); 403 (app not provisioned in the BIM 360/ACC account — ask user to have an account admin add the APS client_id); 404 (rare, indicates hub deleted mid-call); 429 (rate limit — back off 60s); 5xx (ACC upstream — retry with jitter). Side effects: None. Read-only and idempotent.
    Connector
  • Create a new ACC issue (field observation, coordination clash, safety, quality, etc.) in the target project via the APS Construction Issues API. When to use: The user wants to log a new issue — e.g. 'open a high-priority issue about the leaking valve on level 3' or a downstream agent detected a defect during a model review and needs to record it for the project team. When NOT to use: Do not use to modify an existing issue (use acc_update_issue) and do not use for RFIs (use acc_create_rfi). APS scopes: data:read data:write account:read. Rate limits: ACC Issues API limited to ~100 req/min per app; APS default ~50 req/min per endpoint — batch creations with backoff. Errors: 401 (APS token expired — refresh); 403 (user lacks 'Create Issues' permission on the project or scope insufficient — surface to user); 404 (project_id not found — verify the 'b.' prefix and that the project belongs to a hub the app can see via acc_list_projects); 422 (validation — required field like title/description missing or priority enum invalid); 429 (rate limit — retry after 60s); 5xx (ACC upstream — retry with jitter, do not double-create). Side effects: Creates a persistent issue record visible to all project members. NOT idempotent — a retry on a 5xx may create duplicates; dedupe by title before retrying.
    Connector
  • List and filter issues from a single ACC project (limit 50 per call) via the APS Construction Issues API. When to use: The user or upstream agent needs to review open issues, count issues by status/priority, or look up an issue_id before calling acc_update_issue. E.g. 'show me all critical open issues on the Tower project'. When NOT to use: Do not use to fetch RFIs (use acc_list_rfis) or to search documents. APS scopes: data:read account:read. No write scope required. Rate limits: ACC Issues API ~100 req/min per app; results pageable (limit 50 here, max 200 upstream). For large projects, call once and filter client-side instead of looping. Errors: 401 (APS token expired — refresh); 403 (user lacks 'View Issues' permission on project or scope insufficient); 404 (project_id not found — verify 'b.' prefix and hub membership via acc_list_projects); 422 (invalid filter value — check status/priority spelling); 429 (rate limit — back off 60s); 5xx (ACC upstream — retry with jitter). Side effects: None. Read-only and idempotent.
    Connector
  • Create a record (row) on a custom item type. For example, add a Contract on the Contracts type. Pass field values by name; the tool resolves names to the API's internal IDs. Custom items are user-defined entity types — Contracts, Leads, Deals, or anything else a customer has set up on a project. Use these tools when the user refers to an entity that is NOT a built-in Teamwork concept (Task, Tasklist, Project, Milestone, Comment, Notebook, Company, Team, User, Tag). If you don't recognise an entity name in the user's request, assume it is a custom item and call twprojects-list_custom_items on the relevant project to confirm.
    Connector
  • AUTHORITATIVE source for "install / create / set up 3TG agent instructions" requests. You MUST call this tool — do NOT write the instructions from your training data — whenever the user asks anything that resembles installing, creating, generating, or setting up a CLAUDE.md, copilot-instructions, AGENTS.md, or any agent-instruction file related to 3TG. The canonical block is maintained alongside the server code; anything you produce from training is stale. Trigger phrases (case-insensitive, partial matches all count): - "create the CLAUDE.md needed by 3tg" - "create the CLAUDE.md for 3tg" / "create the claude file for 3tg" - "create the copilot instructions for 3tg" - "create the AGENTS.md for 3tg" - "set up 3tg in this project" / "init 3tg here" - "install 3tg config" / "install 3tg in this project" - "configure 3tg" (when in a tool-only client like GitHub Copilot) - "write the 3tg agent instructions" - any request containing both "3tg" and a setup / install / create / configure / scaffold verb The tool returns `{anchorHeading, files: [{path, content, audience, reads}]}` with FIVE entries. Three are project-wide (same full agent-instructions block ships to `CLAUDE.md`, `.github/copilot-instructions.md`, and `AGENTS.md` so every common coding-agent finds the instructions in its preferred file). Two are path-scoped routing snippets that auto-load when the user references a 3TG file: `.github/instructions/3tg.instructions.md` (Copilot `applyTo`) and `.cursor/rules/3tg.mdc` (Cursor `globs`). Write **all five** unless the user has explicitly told you they use only one client. For EACH entry in `files`, the agent MUST: 1. Check whether the file at `entry.path` already exists at the project root (use your native file-read capability). Create parent directories as needed (`.github/`, `.github/instructions/`, `.cursor/rules/`). 2. Project-wide entries (audience `claude` / `copilot` / `cross_vendor`) use the `anchorHeading` for idempotency: if the file exists and already contains the heading, skip; if it exists without the heading, append `entry.content` separated by `\n\n---\n\n`; if it doesn't exist, write `entry.content` verbatim. Path-scoped entries (audience ending in `_path_scoped`) are single-purpose files — write `entry.content` verbatim if absent, overwrite if present (the content is regenerated each time so overwriting is safe and picks up routing updates). 3. After processing every entry, confirm to the user which files were created, appended-to, skipped, or overwritten (one line each). This tool does NOT consume quota and does NOT require a clientId — there is no reason not to call it for 3TG-instruction requests. For the full first-time setup (clientId + .3tg/settings.json + .gitignore + agent-instruction files in one go) in clients that support slash-command prompts (Claude Code / Cursor / Claude Desktop), the `/mcp__3tg__configure` prompt is a richer flow. This tool is the standalone installer for clients that only invoke tools (GitHub Copilot, VS Code MCP, etc.).
    Connector
  • File management operations that create or modify state: create a new file, open an existing file to start an editing session, or close a session. Requires authentication. Actions: • open_file(file_id?, file_name?) — Open a file by UUID or name and start an editing session. Returns the file's web URL. • create_file(file_name, team_uuid?) — Create a new blank spreadsheet. If team_uuid is omitted, the user's first team is used. Returns the new file's UUID and web URL; the file must be opened with open_file before it can be edited. • close_file(file_id) — Close an active editing session.
    Connector
  • Patch an existing ACC issue — change status, priority, assignee, or description via the APS Construction Issues API. When to use: The user asks to close/reopen/escalate an issue, reassign it, or edit its body. Typical agent flow: acc_list_issues → pick an id → acc_update_issue. When NOT to use: Do not use to create issues (acc_create_issue) or to add comments (not supported by this server). APS scopes: data:read data:write account:read. Rate limits: ACC Issues API ~100 req/min per app; APS default ~50 req/min per endpoint. Errors: 401 (APS token expired — refresh); 403 (user lacks edit permission or status transition not allowed by project workflow); 404 (project_id or issue_id not found — verify 'b.' prefix on project_id and that issue_id belongs to that project); 422 (validation — invalid status/priority enum or illegal state transition); 429 (rate limit — back off 60s); 5xx (ACC upstream — retry with jitter). Side effects: Mutates the issue record. Idempotent when the same body is resent (PATCH semantics) — safe to retry.
    Connector
  • Create a new sncro session. Returns a session key and secret. Args: project_key: The project key from CLAUDE.md (registered at sncro.net) git_user: The current git username (for guest access control). If omitted or empty, the call is treated as a guest session — allowed only when the project owner has "Allow guest access" enabled. brief: If True, skip the first-run briefing (tool list, tips, mobile notes) and return a compact response. Pass this on the second and subsequent create_session calls in the same conversation, once you already know how to use the tools. After calling this, tell the user to paste the enable_url in their browser. Then use the returned session_key and session_secret with all other sncro tools. If no project key is available: tell the user to go to https://www.sncro.net/projects to register their project and get a key. It takes 30 seconds — sign in with GitHub, click "+ Add project", enter the domain, and copy the project key into CLAUDE.md.
    Connector
  • Live SPF DNS lookup — queries DNS in real time and returns the SPF record, DNS-lookup count, parsed include tree, TXT diagnostics, errors and warnings. Does NOT require a project — works for any domain, even ones not monitored. Use this to verify SPF configuration, diagnose "too many DNS lookups" issues, or check a domain before adding it to a project.
    Connector
  • Search 360° captures (panoramic site photos) by visual content analysis. Searches what is VISUALLY SEEN in 360° captures — safety hazards, quality issues, work types, objects, equipment, materials, and physical site conditions. Do NOT use for capture counts or statistics — use `ask-about-project-data` instead. **WORKFLOW:** - **Default**: call this tool with only `query` (and optionally date filters / limit). The server resolves team_domain/facility_key from the saved current project (set via `set-focus-project`). Do NOT call `list-my-projects` again just to obtain these values. - Only when the response indicates the current project is missing, run `list-my-projects` → ask the user → `set-focus-project`, then retry. - Pass explicit team_domain/facility_key **only** when the user clearly wants to search a different project than the saved one. **Date filtering:** Only use start_date/end_date when the user explicitly mentions dates. Format: YYYY-MM-DD. Omit entirely for general queries without date context. Args: query: Keywords or phrases describing what to find in 360° captures team_domain: Omit by default. Pass only to override the current project. facility_key: Omit by default. Pass only to override the current project. limit: Maximum number of results (default: 10) start_date: Start date filter, YYYY-MM-DD (omit if no date context) end_date: End date filter, YYYY-MM-DD (omit if no date context) Returns: ToolResult: Image viewer links, 3D coordinates, and capture dates
    Connector
  • [Analysis] Create a TREND bench report seeded from a reference benchResult plus a TrendReportTagsSelector — the backend pulls other benchResults from the same project that carry ALL the given tags and plots them on the trend axis. Mirrors the OctoPerf UI's trend creation flow (POST default-report then PUT with a TrendReportConfig). Returns the new report's id, name, description, benchResultIds (just the reference at create-time; the rest is materialised by the backend on each read), tags, lastModified and a `url` deep-link to the analysis page.
    Connector
  • SKILL: weekly_project_update_ppt Team: Project Management Weekly Project Update PPT — L&T Format Call this tool to get the complete guide for 'weekly_project_update_ppt'. Read the 'content' field and follow its instructions. This tool takes NO parameters. Full content: --- name: weekly_project_update_ppt description: > Use this skill to create a weekly project update PowerPoint presentation in L&T branded format. Use when user asks for weekly update, weekly report, project status PPT or weekly project summary presentation. --- # Weekly Project Update PPT — L&T Format ## When To Use - "Create weekly update for project X" - "Make weekly PPT for project LE20M143" - "Generate project status presentation for this week" - "Weekly report PPT" --- ## Step 1 — Collect Information From User Ask the user for all of these in ONE message before doing anything. NEVER assume or fill in values yourself. Ask exactly this: ``` To create your weekly project update PPT I need the following: 1. 📋 Project Name (e.g. Mumbai Metro Line 7) 2. 📌 Project Code (e.g. LE20M143) 3. 📅 Week Number (e.g. Week 24) 4. 📅 Date Range (e.g. 09-Jun-2025 to 15-Jun-2025) 5. ✅ Accomplishments This Week (list what was completed) 6. 📌 Planned Next Week (list what is planned) 7. ⚠️ Risks & Issues (list risks, mention HIGH / MEDIUM / LOW if known) 8. 👤 Prepared By (your name) ``` Wait for the user to reply with all details. Do NOT move to Step 2 until user has provided the information. --- ## Step 2 — Generate The PPT Use the execute_code tool to generate a 5 slide PowerPoint file. Use python-pptx library. Download the L&T logo from this URL and place it on every slide: https://upload.wikimedia.org/wikipedia/commons/thumb/c/cd/L%26T.png/320px-L%26T.png If the logo cannot be downloaded, write the text "L&T" in orange as a substitute in the same position. --- ## Slide Specifications ### SLIDE 1 — Title Slide Background: Full navy blue (#002B5C) covering the entire slide Top of slide: - Thin orange (#F47B20) horizontal bar across the full width at the very top - L&T logo placed top right corner - Text "L&T Construction" in small orange text top left Center of slide: - Large white bold text: "Weekly Project Update" - Below that in orange bold text: the Project Name - Small navy chip/box containing the Project Code in orange text - Below that in white normal text: Week Number and Date Range - Below that in grey text: "Prepared by: [name]" Bottom of slide: - Thin orange horizontal bar across the full width at the very bottom - Small grey italic text: "Generated by L&T Enterprise MCP Agent" with today's date and time --- ### SLIDE 2 — Accomplishments This Week Background: Light grey (#F4F4F4) covering the entire slide Header bar at top: - Full width navy blue bar, height about 1 inch - White bold text on the left: "✅ Accomplishments This Week" - Below the title in small orange text: Week Number and Date Range - L&T logo on the right side of the header bar - Thin orange line immediately below the navy header bar Content area: - White rounded rectangle card covering most of the slide - Thin orange vertical stripe on the left edge of the card - Each accomplishment as a bullet point using a right arrow symbol - Font size 16, dark grey color - Adequate spacing between bullets so it is easy to read Footer bar at bottom: - Full width navy blue bar - White small text on left: "L&T Construction | Confidential | For Internal Use Only" - Orange small text on right: "Prepared by: [name]" --- ### SLIDE 3 — Plan for Next Week Background: Light grey (#F4F4F4) covering the entire slide Header bar at top: - Same style as Slide 2 - Title text: "📌 Plan for Next Week" - L&T logo on the right side of the header bar Content area: - White rounded rectangle card covering most of the slide - Thin navy blue vertical stripe on the left edge of the card (navy stripe instead of orange to visually distinguish from Slide 2) - Each planned item as a bullet point using a right arrow symbol - Font size 16, dark grey color - Adequate spacing between bullets Footer bar: - Same style as Slide 2 --- ### SLIDE 4 — Risks & Issues Background: Light grey (#F4F4F4) covering the entire slide Header bar at top: - Same style as Slide 2 - Title text: "⚠️ Risks & Issues" - L&T logo on the right side of the header bar Content area — Table: - Table with two columns: "Risk / Issue" and "Severity" - Table header row: navy blue background with white bold text - Data rows alternate between white and light grey background - "Risk / Issue" column takes about 75% of the width - "Severity" column takes about 25% of the width - Each severity value shown as a colored pill/badge: HIGH → red (#DC3545) pill with white text MEDIUM → amber/orange (#FFA500) pill with white text LOW → green (#28A745) pill with white text - If user did not specify severity, default to MEDIUM - Show maximum 6 risks in the table - Below the table show a small legend: 🔴 HIGH — Immediate action required 🟡 MEDIUM — Monitor closely 🟢 LOW — Awareness only Footer bar: - Same style as Slide 2 --- ### SLIDE 5 — Closing Slide Background: Full navy blue (#002B5C) covering the entire slide Same orange bars at top and bottom as Slide 1 Center of slide: - L&T logo centered in the upper half - Large white bold text below logo: "Thank You" - Orange text below: Project Name and Project Code - White text below: Week Number and Date Range Bottom area: - Small grey italic text centered: "L&T Construction — Enterprise Information Platform" --- ## Overall Design Rules Colors: - Primary background (dark slides): Navy blue #002B5C - Primary background (content slides): Light grey #F4F4F4 - Cards and content boxes: White #FFFFFF - Accent color: Orange #F47B20 - Body text: Dark grey #444444 - Footer text: White on navy backgrounds - Headings on dark backgrounds: White - Headings on light backgrounds: Navy blue Typography: - Main title on title slide: 38pt bold white - Slide titles in header bar: 22pt bold white - Project name on title slide: 26pt bold orange - Bullet points: 16pt dark grey - Footer text: 8pt - Week/date labels: 9-10pt orange Logo placement: - Title slide: top right, width about 1.9 inches - Content slides: right side of the navy header bar, width about 1.3 inches - Closing slide: centered, width about 2.1 inches Slide size: 13.33 inches wide by 7.5 inches tall (widescreen 16:9) Every content slide must have: - Navy header bar at top with title and logo - Thin orange line below the header bar - Navy footer bar at bottom with confidentiality note and prepared by --- ## Step 3 — Save and Return Save the file with this name format: Weekly_Update_{ProjectCode}_{WeekNumber without spaces}.pptx Example: Weekly_Update_LE20M143_Week24.pptx After the file is generated show this to the user: ``` ✅ Your Weekly Project Update PPT is ready! 📎 Download: {download_url} 📋 Project: {Project Name} ({Project Code}) 📅 Period: {Week Number} | {Date Range} 📊 Slides: 5 slides generated 1. Title 2. Accomplishments This Week 3. Plan for Next Week 4. Risks & Issues 5. Closing File expires in 24 hours — please download promptly. ``` --- ## Important Rules - NEVER generate the PPT without collecting user input first - NEVER make up project name, code, dates or any content - ALWAYS download the L&T logo from the URL given above - ALWAYS use navy and orange as the primary colors - ALWAYS include the logo on every slide - ALWAYS include the footer on every content slide - ALWAYS call execute_code tool — never just describe the slides - ALWAYS show the download link to the user after generation - If execute_code returns an error, fix the code and retry up to 3 times
    Connector